Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Writing Secure Code... |
|---|---|
| Date: | Wed, 19 Jan 2005 08:29:54 -0500 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have been reading the list for awhile, I think its time I comment. :)
Yes, DJB's djbdns is a 'pretty secure' application. But thats only when you compare it to other DNS packages available, such as BIND, and take into consideration what its code is being audited for. However DJB only makes his security guarntee with certain vulnerabilities in mind. You can read his security guarantee here http://cr.yp.to/djbdns/guarantee.html
A 100% secure application is nearly impossible, this is true. But this does not mean an application cannot be immune to a class of particular vulnerabilities (stack overflows for example). But with features comes complexity and eventually more vulnerable code. Tommorow a new class of vulnerabilities could emerge, and with it could come advisories for djbdns.
MLS is the best line(s) of defense.
Just my two cents.
Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFB7mDQXpi1p4x0qXsRAokfAKCF/S9Z05iRmMZr+4zVTe4aZQB1cQCgo6bM oddTtllYgK5Ae9k679Pfb/Q= =mQHv -----END PGP SIGNATURE-----
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Writing Secure Code..., Michael Silk |
|---|---|
| Next by Date: | Authorization Framework., Babu Kopparam |
| Previous by Thread: | Re: Writing Secure Code..., exon |
| Next by Thread: | RE: Writing Secure Code..., Michael Silk |
| Indexes: | [Date] [Thread] [Top] [All Lists] |