Date: Sun, 28 Oct 2001 09:25:54 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: Mike Barcroft <mike@FreeBSD.ORG>, hackers@FreeBSD.ORG Subject: Re: syslogd and kqueue Message-ID: <3BDC3FA2.20D5D914@mindspring.com> References: <20011026233957.A9925@parhelion.firedrake.org> <20011026200436.A61058@xor.obsecurity.org> <20011027043342.A18231@parhelion.firedrake.org> <20011027001704.B2586@coffee.q9media.com> <3BDAFD1C.B7BF7ED4@mindspring.com> <p05101005b800e4c90608@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosihn wrote: > >Until newsyslog is fixed to not be able to stage a > >denial of service attack against you, I really, really > >recommend against its use. > > Seems like it would be more user-friendly (to freebsd users > in general) to fix newsyslog, instead of just telling people > that they should not use it... If people "just don't use" > newsyslog, how does that guarantee that whatever they do > use will not have the same problem that you described? They will have to make their own solutions correct. Every engineer is responsible for the correctness of their code. All I'[m saying here is that there is a known level of incorrectness in newsyslog: use it at your peril. If you want to fix it, I'm sure people would appreciate the effort. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BDC3FA2.20D5D914>