full-disclosure - Re: OpenBSD Paradox

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikYzCYbYYkC+jsd2=zDO5kAupqTPc+caWFdUG20@mail.gmail.com>
Date: Wed, 15 Dec 2010 23:52:06 +0000
From: Benji <me@...ji.com>
To: musnt live <musntlive@...il.com>
Cc: full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com,
	Theo de Raadt <deraadt@....openbsd.org>
Subject: Re: OpenBSD Paradox

Out-of-troll-mode;

Although I do see that it is probably all FUD, musnt live makes some valid
points.

At the moment OpenBSD just lost a few (more, if you count cvs's being
rooted) trustworthyness-points, which can only be rectified with an audit of
IPSEC coden (initially). Until this is done, OpenBSD will have a hard time
regaining reputation.

On Wed, Dec 15, 2010 at 8:43 PM, musnt live <musntlive@...il.com> wrote:

> On Wed, Dec 15, 2010 at 3:22 PM, Theo de Raadt <deraadt@....openbsd.org>
> wrote:
> >> We has OpenBSD tell us:
> >>
> >> "We have never allowed US citizens or foreign citizens working in the
> >> US to hack on crypto code"
> >> http://marc.info/?l=3Dopenbsd-tech&m=3D129237675106730&w=3D2
> >
> > That statement remains true.
>
> > Our project permitted American developers to work on any part of the
> > tree which was not specifically cryptography; in this particular
> > instance that includes the parts of IPSEC which are 'dual use' or 'not
> > related to cryptography'.  We did not permit them to work on the
> > crypto-specific parts.
> >
>
> Military is clever at words and dual use for is example, dual use of
> technology.
>
> So is your approach: "He is not backdoor crypto! Only the portion on
> the network - so is your data sniffable"
>
> In all wording from OpenBSD, there is not one denial: "IPSEC is not
> backdoored" only word trickery:
>
> "We is full disclosing someone say IPSEC is backdoor"
> "We is full disclosing IPSEC is not worked on by Americans"
> "We is receive strange email"
> "We is have DARPA funding cut!"
>
> Never have we see:
>
> "OpenBSD is not backdoored"
> "OpenBSD audited is this code in the past"
> "OpenBSD is currently going back to is audit"
>
> Furthermore is fact that is as developer, one developer can seek help
> from another developer and this is developer who put backdoor:
>
> CryptoDeveloper = I has no idea how is to make this work
> RogueDeveloper = I is has this special piece of code is for you
> CryptoDeveloper = Is thanks!
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/