[syslog-ng]Reciving data from non RFC compliant devices

[Michael Boman]

--=-PXV0b3icF1E7ir1Tr+iJ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I just got another syslog-generating machine to monitor, and it seems it
doesn't follow the syslog RFC as it sends out messages with ^I (tabs).

I was thinking about hacking syslog-ng in such way it will enforce RFC
compliance of the "message" part for the data. Basically I am thinking
about replacing char <=3D 31 and char >=3D 127 with a space.

Question:
 - Any reason why _not_ to do this?
 - Which function is the best place to hack the code in?


Best regards
 Michael Boman

--=20
Michael Boman
Security Architect, SecureCiRT Pte Ltd
http://www.securecirt.com

--=-PXV0b3icF1E7ir1Tr+iJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA+40dRds5fQJiraJwRAswHAJ9TQnHNczJPkazO5LNtSEtZfR0KPgCdFCrV
VHif4V85BYTgWoJbSx7NekI=
=ou6/
-----END PGP SIGNATURE-----

--=-PXV0b3icF1E7ir1Tr+iJ--