umputun / dkll / 32346082648

83%

push

github

Fix panic on truncated syslog lines

Previously, NewEntry sliced the line by the offset of the host and the
service token without checking that anything follows them, so a line
ending right after the timestamp, the host or the service token panicked
with an index out of range. The same applied to the RFC3339 branch of
parseTime when the line carried nothing but a timestamp. Since the syslog
server accepts unauthenticated UDP and TCP input, such a line terminated
the whole process.

After this change both use strings.Cut and return an error for a line with
a missing token or separator, so the forwarder logs it and carries on.

16 of 16 new or added lines in 1 file covered. (100.0%)

1018 of 1224 relevant lines covered (83.17%)

17811.76 hits per line