[syslog-ng] [Bug 178] Spoofed source address bug introduced in 3.3.5

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Wed Jul 11 15:48:30 CEST 2012


--- Comment #15 from Marvin Nipper <marvin.nipper at stream.com>  2012-07-11 15:48:30 ---
>>but that will mean that if a host is not resolvable at reload time,
>> then it won't be retried, and the same bug will surface -
>> just less often, and under rare circumstances.

Well, that would obviously "not be desirable" either, as it basically means "random" failures, and loss of data (that should have been forwarded), which will
then not be easy to parse out and (so to speak) "re-forward" to the intended target.

I'm guessing that you really weren't asking me for anything anyway(??), but were simply lamenting the conundrum that has resulted from the original patch, that
introduced this spoofing problem.  (And I've certainly lamented over my own coding nightmares in the past, so I sympathize!)

Let me know if you need anything from me.  I'm obviously more than happy to test some other variation that you might come up with.  Apologizes for not being
familiar enough with the syslog-ng coding to dive in and provide any help.

Thanks again for all of your efforts!

Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list