Re: [Full-disclosure] Allegations regarding OpenBSD IPSEC
- From: Steve Pinkham <steve.pinkham@xxxxxxxxx>
- Date: Wed, 15 Dec 2010 14:15:53 -0500
On 12/15/2010 01:32 PM, Paul Schmehl wrote:
--On December 14, 2010 8:40:14 PM -0500 bugs@xxxxxxxxxxx wrote:examining
So for 10 years IPSEC has had a backdoor in it and not one person
the code has noticed it? Or even questioned it? That's a bit hard tocaptures
believe. It's along the same lines as the stories that Microsoft
all your packets and harvests your personal information.
Read The Cathedral and The Bazaar.
Yeah, just like there was no way to miss the SSL renegotiation flaw for
so many years. Or "The Kaminsky Bug". Or the recent downgrade flaw in
OpenSSL. Or..
Note all those examples are (assumed?) non-malicious. Imagine if really
knowledgeable programmers and crypto people got together to try to hide
such things. See the "Underhanded C" contest for examples.
http://underhanded.xcott.com/
This stuff is *hard*, and talent is valuable and already spread thin.
--
| Steven Pinkham, Security Consultant |
| http://www.mavensecurity.com |
| GPG public key ID CD31CAFB |
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
- References:
- [Full-disclosure] Allegations regarding OpenBSD IPSEC
- From: bugs
- Re: [Full-disclosure] Allegations regarding OpenBSD IPSEC
- From: Paul Schmehl
- [Full-disclosure] Allegations regarding OpenBSD IPSEC
- Prev by Date: [Full-disclosure] WordPress cformsII plugin CAPTCHA bypass vulnerability
- Next by Date: Re: [Full-disclosure] OpenBSD IPSEC has backdoor
- Previous by thread: Re: [Full-disclosure] Allegations regarding OpenBSD IPSEC
- Next by thread: Re: [Full-disclosure] Allegations regarding OpenBSD IPSEC
- Index(es):