|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: patch for qpopper remote exploit bug
Theo de Raadt (deraadt
CVS.OPENBSD.ORG)Sat, 27 Jun 1998 16:50:40 -0600
- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Bruno Lopes F. Cabral: "Re: QPOPPER problem...."
- Previous message: Yiorgos Adamopoulos: "Re: QPOPPER problem.... ONE crude patch..."
- In reply to: Andres Kroonmaa: "Re: patch for qpopper remote exploit bug"
- Next in thread: Jon Lusky: "Re: patch for qpopper remote exploit bug"
Yeah, but what about systems that do _not_ have vsnprintf()? Using calls without bounds checks can be justified as long as it is made dead sure that no bounds would be ever exceeded. You complain to your vendors. This is a function which every vendor should have in their libraries. If they don't, I can promise you that OS has not been audited, and that 10 or so bugs in libc exist which will bite you. Today, snprintf and vsnprintf are required. Without them, there's some code in the libraries which cannot be written safely. ie: gen/syslog.c: prlen = vsnprintf(p, tbuf_left, fmt_cpy, ap); Hmm.
- Next message: Bruno Lopes F. Cabral: "Re: QPOPPER problem...."
- Previous message: Yiorgos Adamopoulos: "Re: QPOPPER problem.... ONE crude patch..."
- In reply to: Andres Kroonmaa: "Re: patch for qpopper remote exploit bug"
- Next in thread: Jon Lusky: "Re: patch for qpopper remote exploit bug"