Slashdot Mirror


BSD Coder Denies Adding FBI Backdoor

jfruhlinger writes "Theo de Raadt has made the shocking claim that OpenBSD includes a backdoor that the FBI paid coders to build. Brian Proffitt has tracked down one of the programmers named as being on the FBI payroll (actually, he tracked down two programmers with the same name). Both deny working with the FBI."

182 of 239 comments (clear)

  1. Please correct. by santax · · Score: 5, Informative

    It was not Theo that made that claim. It was Theo that released the email he got from the guy making that claim! Big big difference!

    1. Re:Please correct. by skids · · Score: 2, Insightful

      I would go on a rant about how anyone who wants to post main stories should really be forced to attend at least a half-day seminar on basic journalistic essentials.

      But considering how an entire degree in journalism does not seem to have helped the professional media....

    2. Re:Please correct. by delt0r · · Score: 1

      So instead of Some guys found something, its I know a guy who think he found something.... Yea really credible.

      --
      If information wants to be free, why does my internet connection cost so much?
    3. Re:Please correct. by santax · · Score: 5, Informative

      You haven't read that mail if you are saying that. Just read the damn mail! http://marc.info/?l=openbsd-tech&m=129236621626462&w=2

    4. Re:Please correct. by jfruhlinger · · Score: 5, Informative

      I'm the one who submitted it to Slashdot, and it's totally my fault, not a mistake in TFA. Apologies.

    5. Re:Please correct. by skids · · Score: 2

      You mean they believe things like "I have received a mail" and "It is alleged..."? How horrible.

      Or do you mean that CmdrTaco being who he is, people believe what he says Theo has to say.

    6. Re:Please correct. by John+Hasler · · Score: 5, Insightful

      It isn't totally your fault. It is also the fault of the Slashdot editor who didn't bother to read the article.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    7. Re:Please correct. by santax · · Score: 1

      You are forgiven my son. Just stay clear from ssh on openbsd for now. Cause I'm not sure Theo will forgive you too :P

    8. Re:Please correct. by tenchikaibyaku · · Score: 4, Insightful

      Even if there's no truth whatsoever behind the initial claim, I suspect we'll be seeing this pop up in various more and less accurate forms for several years to come.

    9. Re:Please correct. by at_slashdot · · Score: 1

      Damn, what a misleading title. Thanks for explanation.

      --
      "It is our choices, Harry, that show what we truly are, far more than our abilities." -- Prof. Dumbledore
    10. Re:Please correct. by Lumpy · · Score: 1

      It works for the MOB and gangs... want a rival killed? start rumors they are working for the cops, fbi, are dirty and skimming from the boss, etc.. Keep it up and word wil spread and get back to his guys who end up "fixing the problem".

      Works in the non-cime world as well. Sysadmin acting like a BOFH? start planting small rumors he is stealing or hacking from work. Want to put questions in the minds of people who might switch from windows? put out there a "rumor" that it has Government backdoors in it.

      FUD works great in all walks of life.

      --
      Do not look at laser with remaining good eye.
    11. Re:Please correct. by 0123456 · · Score: 1

      It works for the MOB and gangs... want a rival killed? start rumors they are working for the cops, fbi, are dirty and skimming from the boss, etc.. Keep it up and word wil spread and get back to his guys who end up "fixing the problem".

      Interestingly, I was reading this morning about the FBI in the 70s spreading false claims that members of radical groups were actually FBI informants in the hope of disrupting said radical groups.

    12. Re:Please correct. by bsDaemon · · Score: 1

      Or do you mean that CmdrTaco being who he is, people believe what he says Theo has to say.

      Well, some people are new here...

    13. Re:Please correct. by kaiser423 · · Score: 1

      The fact that Theo used his position of power to show the email to everyone does mean that he is at least tacitly endorsing and/or making the claim. Otherwise he could have just ignored it.

    14. Re:Please correct. by Lennie · · Score: 2

      'Want to put questions in the minds of people who might switch from windows? put out there a "rumor" that it has Government backdoors in it.'

      Actually, if it is in OpenBSD, then you can be damn sure it is Windows too.

      --
      New things are always on the horizon
    15. Re:Please correct. by daremonai · · Score: 1

      We can forgive you for this, but not for how you did on Jeopardy.

    16. Re:Please correct. by jfruhlinger · · Score: 1

      O CRUEL REMINDER! *sobs*

    17. Re:Please correct. by Obfuscant · · Score: 1
      The fact that Theo used his position of power to show the email to everyone does mean that he is at least tacitly endorsing and/or making the claim. Otherwise he could have just ignored it.

      After reading TFA, I came to the conclusion that Theo believes it is true. He used the excuse that exposing the dastardly FBI shenanigans justified the posting of a private email. If you don't think the FBI did it, you can't use it as the excuse for posting the email.

      It would have been nice if the claim came with a reference to the code that was inserted. "I believe it enough to use it as an excuse to post private email from someone I don't like, but not enough to bother looking at the code to see if it really happened" is kinda lame.

      I say that knowing I wouldn't know what to look for, but he would.

    18. Re:Please correct. by clone52431 · · Score: 2, Informative

      a private email

      It was his e-mail, because it was sent to him. He’s the one who gets to decide whether it’s private or not.

      There is someone else’s private e-mail, and then there is my e-mail. Whether or not I want my e-mail to be private is my decision. If you send me an e-mail, unless you specifically request otherwise, assume I can do whatever I want with it. Including post it online.

      --
      Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
    19. Re:Please correct. by houghi · · Score: 1

      You must be new here.

      --
      Don't fight for your country, if your country does not fight for you.
    20. Re:Please correct. by Yossarian45793 · · Score: 1

      It's not totally the fault of the editors. It's also the fault of the readers who come back to Slashdot expecting the editors to start reading articles when they have clearly demonstrated that they do not plan to.

    21. Re:Please correct. by geminidomino · · Score: 1

      Whether or not I want my e-mail to be private is my decision. If you send me an e-mail, unless you specifically request otherwise, assume I can do whatever I want with it. Including post it online.

      Actually, even if they DO request otherwise, you can still do whatever you want with it. It might make you a dick, but its still your right!

    22. Re:Please correct. by DamonHD · · Score: 1

      I don't agree.

      In general, IMHO, forwarding on my private email to you without permission is in violation of my copyright, ie I haven't given you permission to copy it to other people, possibly for very good commercial/privacy/other reasons.

      At the very least it's pretty damn rude.

      *However*, there may be many sorts of ways in which I gave implicit permission. For example if it's work related and not obviously super private. Getting someone else involved in the To list may be just the right thing to do.

      And once, when I was editor of a technical rag and someone rather senior at a major US semiconductor company sent me a rant about what an arse I was/am, and didn't say NOT FOR PUBLICATION... Well, letters to the editor are for publishing, yes? (So we had a nice little round-up in print of commentary from major competitors about how maybe, just maybe, in this case, I wasn't the arsehole in the exchange. Sweet revenge and actually rather proved my point at the time that was being so violently disputed I think.)

      But you do need good grounds IMHO before disclosing private correspondence: the other party has a stake in it too and it's not just "yours" unless say you paid for it "work for hire"...

      Rgds

      Damon

      --
      http://m.earth.org.uk/
    23. Re:Please correct. by clone52431 · · Score: 1

      In general, IMHO, forwarding on my private email to you without permission is in violation of my copyright, ie I haven't given you permission to copy it to other people, possibly for very good commercial/privacy/other reasons.

      It could fall under fair use, though. Specifically, posting it in order to criticize/comment on it:

      The practical effect of this law and the court decisions following it is that it is usually possible to quote from a copyrighted work in order to criticize or comment upon it, teach students about it, and possibly for other uses.

      However in this case I think it’s even more obviously fair use (if you can consider the e-mail to be copyrighted), because it is implied when someone gives a tip like this that they expect you to do something about it, which probably includes telling where the tip came from. Unless, perhaps, they specifically asked to remain an anonymous source.

      --
      Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
    24. Re:Please correct. by rtfa-troll · · Score: 1

      There's one other thing. Theo has always stood up for full disclosure. He's regularly gets flack for not doing it enough. He may have also feared that this was a trap, to prove that he keeps things that should be public secret. In fact, given that it seems it's largely or completely untrue, it easily could have been a trap that he didn't fall into. This is just the side effect of him making the best of a bad hand.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    25. Re:Please correct. by rvw · · Score: 1

      It isn't totally your fault. It is also the fault of the Slashdot editor who didn't bother to read the article.

      The editor didn't RTFA? Only on Slashdot! :-P

    26. Re:Please correct. by DamonHD · · Score: 1

      Sure: my point is that it is NOT reasonable to assume that it's OK to forward something verbatim or in large part UNLESS one has a good reason.

      Ie the default should be to assume that you have no automatic right to do so.

      Copyright would only be one reason.

      Rgds

      Damon

      --
      http://m.earth.org.uk/
    27. Re:Please correct. by SLi · · Score: 1

      Ah, the classic way of trying to misuse copyright to hide embarrassing facts about you. In most cases that got to courts it was eventually determined that most emails are not creative enough to warrant copyright protection, and the fact that your motive is to hide the facts, not protect the specific expression of those facts, also speaks against you. Plainly, that's not what copyright is for, and the courts don't usually sanction trying to use it for that. One factor against copyright in this particular case is that the message was highly fact (or allegation) rich and not some elaborate prose warranting copyright protection.

      Moreover, you can only ever claim copyright on the expression, not the particular facts in the message. Even in the rare case where your message enjoyed copyright protection, nothing would prohibit the recipient from telling anyone about everything you said in the message in their own words.

      Finally, one important factor against copyright infringement (and for fair use) is that the issues presented are of public importance and that the publication is not done for profit.

      Publishing email sent by you may be rude, but that's really the extent of it.

    28. Re:Please correct. by Obfuscant · · Score: 1

      What you think about private email wasn't the point, or even if there is such a thing as "private email". The point was that Theo made a specific comment about posting a private email and compared the ethical status of that to the insertion of a backdoor by the FBI. This implies that he both considers there to BE ethical implications to posting private email (which you clearly do not) and that the FBI did something that outweighs his own ethical standards regarding posting such.

    29. Re:Please correct. by DamonHD · · Score: 1

      I agree with a lot of that, especially in theory, but I was referring to the notion of forwarding my private emails wholesale without any good reasons/defences such as you mention above.

      So, I still think that the presumption is that you should not publish the *verbatim text* of private emails without good reason. If you paraphrase, for example, then copyright probably does not apply, though in places such as France privacy laws may still, IANAL.

      Rgds

      Damon

      --
      http://m.earth.org.uk/
    30. Re:Please correct. by the_womble · · Score: 1

      You misunderstand journalistic: the priority is to get as many stories about celebrities out as quickly as possible.

    31. Re:Please correct. by geminidomino · · Score: 1

      In general, IMHO, forwarding on my private email to you without permission is in violation of my copyright, ie I haven't given you permission to copy it to other people, possibly for very good commercial/privacy/other reasons.

      As others have said, I doubt even our functionally retarded US courts would go for that.

      At the very least it's pretty damn rude.

      I did acknowledge that fact.

  2. well by stillpixel · · Score: 1

    even if it was you, would you admit to it? Reputations and careers could be ruined by something like that.

    1. Re:well by gstoddart · · Score: 2

      even if it was you, would you admit to it?

      Depending on the situation, they might not legally be able to admit it. If your work was Classified, you might be prohibited by law from admitting to it.

      Not saying that is true or even likely in this case, but it is possible. I wouldn't want to run afoul of a government NDA.

      --
      Lost at C:>. Found at C.
    2. Re:well by mark72005 · · Score: 2

      Warning: People denying the existence of robots may be robots themselves.

    3. Re:well by gstoddart · · Score: 1

      Warning: People denying the existence of robots may be robots themselves

      Well, I have a robot vacuum, so I'm not going to deny their existence.

      However, I can neither confirm nor deny that I am a robot.

      --
      Lost at C:>. Found at C.
    4. Re:well by shentino · · Score: 1

      Not to mention being required to admit to it would probably contradict the 5th amendment.

  3. Re:Oh come on by TheRaven64 · · Score: 4, Insightful

    The difference is that the original story is posted by kdawson, so no registered users will see it, because we've all blocked him from the front page. This one is posted by Taco, so we'll see it.

    --
    I am TheRaven on Soylent News
  4. The whole story seemed a bit off by Fibe-Piper · · Score: 4, Interesting

    I mean the idea that this person would still be alive when "the NDA expired..." was odd.

    Why would the FBI make any NDA on something as shameful as this that would expire during one's lifetime?

    --
    I went to battle M.C. Escher, but drew a blank.
    1. Re:The whole story seemed a bit off by Anonymous Coward · · Score: 1

      This wouldn't be under NDA, it would be classified, and the only way it would be releasable was if it had a declassification date. If that were the case, it would be available under FOIA.

    2. Re:The whole story seemed a bit off by icebike · · Score: 1

      Well it might have existed sometime in the past and been removed long ago, making the point moot.

      That code has had extensive revisions, and anything obfuscated enough to hide a backdoor was probably stripped out long ago in the quest for clarity or simply because no one could understand it and demonstrate that it was correct.

      Especially in security code, it the lead maintainer can't comprehend the code it becomes immediately suspect.

      --
      Sig Battery depleted. Reverting to safe mode.
    3. Re:The whole story seemed a bit off by BobMcD · · Score: 1

      Well it might have existed sometime in the past and been removed long ago, making the point moot.

      Not quite moot, no. Our FBI is prohibited from meddling in our publications (First Amendment) and from eavesdropping without oversight (Fourth Amendment), so even were this immediately removed the very fact that someone attempted to do it is a valid point.

      Especially in security code, it the lead maintainer can't comprehend the code it becomes immediately suspect.

      Yeah, sure, very true. What if the lead maintainer is complicit? What then?

    4. Re:The whole story seemed a bit off by icebike · · Score: 1

      FBI is not prohibited from "meddling in our publications".

      The first amendment simply states:

      Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.

      That does not mean they can not "contribute", or publish, or provide information (true or false) to publishers. All it means is that Congress shall pass no law abridging the freedom of the press.

      Any putative back door's mere existence does not imply use of the back-door without a warrant anymore than possession of a steam iron implies that they read your mail.

      (A warrant would be useless without a back door, which is why they might want that in place ahead of time.)

      (Before you jump on me: I'm not claiming this was never used (legally or illegally), simply making the case that the insertion of a back door does not in itself constitute any illegal act).

      As for the lead maintainer being complicit, that's why its open source, and I suspect many pairs of eyes are looking at this code again this week.

      --
      Sig Battery depleted. Reverting to safe mode.
    5. Re:The whole story seemed a bit off by AHuxley · · Score: 1

      http://en.wikipedia.org/wiki/Magic_Lantern_(software) was an FBI effort, so was http://en.wikipedia.org/wiki/Carnivore_(software).
      The NSA had zero legal limits from day one unlike the CIA, FBI, so they would be the logical subverters of any crypto.
      Within the US you had the long CONINTELPRO issues and the FBI's contact with hackers and the turning of hackers into informants...
      Tthe FBI takes the credit for been in your computer, capturing your network, why not in your networking code too?
      The NSA like the GCHQ can hide in the shadows.

      --
      Domestic spying is now "Benign Information Gathering"
  5. Re:Oh come on by Scutter · · Score: 3, Informative

    You didn't get that this was a follow-up story, then, huh?

    --

    "Tell me doctor, with all of your defenses, are there any provisions for an attack by killer bees?"
  6. Wrong summary by Anonymous Coward · · Score: 3, Informative

    Oh please, de Raadt didn't claim shit. Here's the original mail.

    Theo seems skeptical himself, he just didn't want to hold back a potential security issue.

    1. Re:Wrong summary by lysdexia · · Score: 1

      Precisely. If anyone can find fault with Mr. DeRaadt's handling of this situation (other than the admitted ethical issue of publishing an email without permission of the sender), I'd like to hear the logic.

    2. Re:Wrong summary by kjs3 · · Score: 1, Troll

      Lesse...I'll publish a wildly sensational accusation by a third party without attempting to verify any of it and excuse myself with "prove you didn't do it". Of course, since everyone on the Internet will take a reasoned step back, verify all the facts before reacting, and will never launch a mass electronic lynch mob, the folk accused will be just fine. Does that cover how big a douche DeRaadt is here?

    3. Re:Wrong summary by Lemmy+Caution · · Score: 1

      "Publishing" it by releasing it to the mailing list for people who, um, work on that source code *is* verifying/testing it. He's smart enough to know that a good backdoor could escape the notice of only one (even very smart) individual.

      If this is what you call being a douche, then let me write a check to the Society for the Preservation of Douches.

    4. Re:Wrong summary by kjs3 · · Score: 2

      Not my point. This is probably going to come as quite a surprise to you, and you probably don't much care, but there's more at stake here than the backdoor. Jason Wright, FBI plant or no, will never be able to fully clear his name, and for some will always be "the guy who might be a FBI plant". God help the guy if someone finds some sort of bug; no matter how innocuous, it will be cited as "proof". I clearly don't know how "douche" is defined in your world, but in mine throwing someone under the bus with no hard evidence and precisely zero concern for them qualifies as grade-A douche. But then, I actually give a shit about other people and consider the consequences of my actions. YMMV.

      The adult, professional, dare I say "non-douche" way to handle this would have been to say "I have credible reason to believe that there is a deliberately introduced back door in the IPSec code in OpenBSD. It would have been introduced around $DATE and/or in $FILES. Please drop what you are doing and start auditing." while trying to confirm the details. Obviously, that didn't happen. Obviously, far too many people couldn't care less.

    5. Re:Wrong summary by John+Hasler · · Score: 1

      Unfortunately, "douches" sometimes tell the truth. I tend to doubt the allegations, but I can see that they still must be investigated. Since OpenBSD is a public, Free Software project, the investigation must be public.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  7. NDA by Ismellpoop · · Score: 1

    If you made a deal to keep a secret you keep that secret. Also I'm sure there could be repercussions for blabbing. My job they just fire you and there is a possibility of being sued by the individual whoes confidence you broke.

    1. Re:NDA by PPH · · Score: 1

      I'm sorry, but I'm prohibited by an NDA from discussing any work I may have done for any government organization on that project.

      captcha: confuses

      --
      Have gnu, will travel.
    2. Re:NDA by zn0k · · Score: 3, Informative

      No.

      But that's because they're bound by patient confidentiality, and not a boilerplate 10 year "don't talk about anything you learned at work" NDA.

      So the two cases don't really compare. At all.

    3. Re:NDA by Pi1grim · · Score: 1

      Depends on their NDAs. For crying out loud, read the goddamn definition of NDA and what limitations it might have. There is a completely different thing, called patient (in case of a doctor) or client (in case of a lawyer) confidentiality, where they cannot disclose the data of their patient/client without police warrant. In this case it is told, that the guy had a ten-year NDA signed, ten years have passed, he can talk as much as he wants about that job of his. Simple.

    4. Re:NDA by JonJ · · Score: 2, Funny

      It's no wonder you smell poop, it's coming straight out of your mouth.

      --
      -- Linux user #369862
    5. Re:NDA by John+Hasler · · Score: 1

      Don't be an ass. Professional confidentiality is not the same as an NDA contract, and he didn't claim that all such agreements expire after ten years in any case.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    6. Re:NDA by Qzukk · · Score: 1

      So when you go to your doctor or shrink can they say hey its been ten year I can blab about so and so's mental problems

      If you signed a contract saying after 10 years the doctor can blab all he wants, sure.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    7. Re:NDA by John+Hasler · · Score: 2

      > If you made a deal to keep a secret you keep that secret.

      If I made a deal to keep a secret for five years I keep it for five years.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  8. Re:Oh come on by Jurily · · Score: 3, Funny

    Who's this "kdawson" you speak of?

  9. Well heck, I thought they'd fess up right away. by gestalt_n_pepper · · Score: 1, Funny

    NOT!

    --
    Please do not read this sig. Thank you.
  10. Funny... by cobrausn · · Score: 1

    Back before I used Linux (in college), I made a habit out of making all Linux users paranoid by saying if I were the CIA / FBI / NSA / other TLA, I would worm somebody in as a contributor and do my best to put hidden backdoors into all open source operating systems. I know if I were in any of said agencies and had no respect for privacy, I would.

    --
    How does it feel to be a liar with pants constantly on fire?
    1. Re:Funny... by BESTouff · · Score: 1

      Whereas you can be sure no one at Microsoft or Apple is coding backdoors for a TLA ?

    2. Re:Funny... by bluefoxlucid · · Score: 1

      Actually I use the DOD back door in EFS all the time. I found it while tracing EFS in IDA Pro for an exercise.

    3. Re:Funny... by tlhIngan · · Score: 2

      Whereas you can be sure no one at Microsoft or Apple is coding backdoors for a TLA ?

      More like, you KNOW there are backdoors in Windows, Mac OS X, iOS, and all the other products they have. But don't switch to open-source purely because it's open-source and therefore, backdoors can't be hidden in the code. Even very careful audits can still miss cleverly hidden backdoors.

      The silly thing about this issue is that no one can confirm or deny it, short of a full on hard core code review. The people who did it certainly won't say either way (other than "it might"), the ones who know about it won't acknowledge it. And the backdoor doesn't have to be a shell-granting root access. It can a simple matter of key leakage through subtle means and the code looks otherwise innoculous.

    4. Re:Funny... by Lumpy · · Score: 2

      OF course not. such a coder would be easily spotted because they know what they are doing and produce clean code that works... This will stand out BIG TIME at Microsoft.

      --
      Do not look at laser with remaining good eye.
    5. Re:Funny... by cobrausn · · Score: 1

      tlhIngan hit it on the head. I figured they were there for Microsoft and Apple. I just liked screwing with Linux guys who were insisting they were perfectly secure because they used an open source OS.

      As I said, I use Linux, so I don't have any axe to grind against open source. I'm just suspicious of pretty much everything.

      --
      How does it feel to be a liar with pants constantly on fire?
    6. Re:Funny... by gknoy · · Score: 2

      How do you know they're planted by the DOD, rather than simply programming mistakes that no one caught?

    7. Re:Funny... by bluefoxlucid · · Score: 2

      Hard-coded secondary keys are pretty big programming mistakes. Maybe for debugging, or an old recovery mechanism that was disabled?

    8. Re:Funny... by paeanblack · · Score: 1

      it's open-source and therefore, backdoors can't be hidden in the code

      You really, really, REALLY need to read this:

      http://cm.bell-labs.com/who/ken/trust.html

  11. BSD coder? by Tomun · · Score: 1

    Both deny being BSD coders too!

    1. Re:BSD coder? by aliquis · · Score: 1

      Slashdot joke: Necrocodia? :D

    2. Re:BSD coder? by Java+Pimp · · Score: 1

      Exactly. In the email sent to Theo, Scott Lowe isn't identified as one of the OpenBSD contributors accused of inserting the alleged backdoor.

      He is "accused" of advocating OpenBSD while being on the FBI payroll. Which shouldn't matter anyway since that alone does not confirm a backdoor was actually inserted.

      --
      Ascalante: Your bride is over 3,000 years old.
      Kull: She told me she was 19!
    3. Re:BSD coder? by BatGnat · · Score: 1

      How hard would it be to use an alias? you don't exactly require proof of id to submit anything do you?

      I would deny as well, it if I had done it...

  12. Isn't this expected? by Arrepiadd · · Score: 1

    I'm not familiar with these things, but if someone is installing backdoors for the FBI on some software, will he be telling everyone that he works/has worked with the FBI? I wouldn't really expect anything else other than denying it!

    This doesn't mean he does work for the FBI, but saying he doesn't isn't going to clear all things up!

    1. Re:Isn't this expected? by socz · · Score: 1

      Yeah either way, this is a tiny blow to the BSD's just because it's something one could say against them. All these years of pushing BSD out to everyone and now this! Boy, am I gonna hear it today! Or tomorrow if they don't keep up with the news.

      --
      My abilities are only limited by my imagination
  13. Well it might by Sycraft-fu · · Score: 4, Insightful

    The normal length for classified material is 50 years. That isn't to say it can't last longer or be declassified earlier, but 50 years is the normal NDA length. Why would this be any different? In particular there was the implication that they'd been heavily pushing it because of the backdoor. Ok but they had to know that the NDA was about to expire and thus the jig would be up and it would be, if anything, harmful.

    Makes no sense. I am not buying this in the slightest without some proof. Some guy claiming something in an e-mail isn't proof, that is Internet nuttery as normal.

    1. Re:Well it might by Fibe-Piper · · Score: 2

      The normal length for classified material is 50 years. That isn't to say it can't last longer or be declassified earlier, but 50 years is the normal NDA length. Why would this be any different?

      FTA -

      "...sent to him by Gregory Perry, who worked on the OpenBSD crypto framework a decade ago."

      I think that 50 years sounds normal for an agency whose job has become protecting secrets. A decade does not sound like something that would benefit them at all. That's what seemed strange to me about the original article.

      --
      I went to battle M.C. Escher, but drew a blank.
    2. Re:Well it might by Locutus · · Score: 1

      this reminds me of how the CEO of Green Hills was spreading FUD saying how insure Linux was because anyone could embed backdoors in not only Linux but into gcc. He was trying to say how much better their software was because it was not open source. Some of this stuff just doesn't add up when you look at the bigger picture and what the motivation behind the info often tells the real story. For Green Hills, Linux is a threat to their business model so they wanted to spread FUD to limit its effects. I wonder what the motivation is here?

      Just wondering, are NDA's with the DoD the same duration as the classification of the project or data? As a US citizen, doesn't exposure to classified information require you to keep that information to yourself until it is made public regardless of the NDA you might have signed? I get it that the military is not the government but they are still VERY closely tied.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    3. Re:Well it might by Darinbob · · Score: 1

      Government bureaus are not machines of hyper efficiency. They're just as disorganized and bumbling as any corporation, maybe more so. It is not unreasonable to assume there was a small group of FBI personnel who set this up but then forgot about it later, and upper management may never have known. I can't imagine them adding an Outlook Calendar entry for more than a decade in the future saying "cover your asses today, it's about to blow!"

      This is also the biggest reason I dismiss conspiracy theories, because I can't believe governments are organized well enough to pull off any of the stuff that's claimed.

    4. Re:Well it might by Obfuscant · · Score: 1
      this reminds me of how the CEO of Green Hills was spreading FUD saying how insure Linux was because anyone could embed backdoors in not only Linux but into gcc. He was trying to say how much better their software was because it was not open source.

      I think his argument would be something like this: for Linux, most people will (by default) be trusting the repo designer(s) to not have inserted a backdoor into anything in the repo. That's a relatively large number of people compared to the number that could insert a backdoor into his code.

      While it is true that anyone who is really paranoid will get the source to everything in the repo and recompile it, there is still the issue of what you recompile it with. Either you hand-code in assembly a base-level C compiler that you use to compile the GCC compiler after you examine it for back doors, or you have to trust the source of the pre-compiled gcc compiler not to have put backdoor code into that. And examining the gcc compiler source for backdoors will be a herculean task.

      The fact that Linux is open source means that others can obtain the source and modify it to create back doors, which is a much easier task than recreating the functionality of the code and putting in a trap. For example, I can take the source to crt0.o and add something bad to it much easier than trying to duplicate the initialization process and do the bad thing.

      Everyone has to trust someone at some point. Who do you trust?

  14. The first sentence of the summary is false. by John+Hasler · · Score: 2

    Theo de Raadt has made the shocking claim that OpenBSD includes a backdoor that the FBI paid coders to build.

    Theo did no such thing. Perry did.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  15. What the hell? by mysidia · · Score: 5, Insightful

    There was never any OpenBSD contributor named Scott Lowe. Did anyone actually bother to read the source material or check facts, before claiming as such?

    The finger was being pointed at Scott Lowe FOR HIS Virtualization BLOG, which are merely articles that discuss the use of OpenBSD.

    The mailing list author, was making a totally reckless claim with no proof shown that He was advocating OpenBSD for the benefit of the FBI which is downright ludicrous attention whoring attempt on the part of someone reposting that claim without corroboration.

    A mailing list posting by one person is not a credible source to be taken at face value. Information needs to be corroborated. Posting some random person's vague accusations as front page news borders on gross negligence.

    1. Re:What the hell? by John+Hasler · · Score: 2

      > There was never any OpenBSD contributor named Scott Lowe.

      I don't see where Perry claimed that there was.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    2. Re:What the hell? by Java+Pimp · · Score: 1

      There was never any OpenBSD contributor named Scott Lowe.

      I don't see where Perry claimed that there was.

      He didn't. But TFA does...

      --
      Ascalante: Your bride is over 3,000 years old.
      Kull: She told me she was 19!
    3. Re:What the hell? by Java+Pimp · · Score: 1

      Actually, not even TFA does, only the Slashdot summary... which shouldn't surprise anyone...

      --
      Ascalante: Your bride is over 3,000 years old.
      Kull: She told me she was 19!
    4. Re:What the hell? by mzs · · Score: 1

      Exactly, the article author should contact Jason Wright and his associates for comment.

    5. Re:What the hell? by BatGnat · · Score: 1

      Seriously?

      If you were hired by the FBI to inject a backdoor into open source code, wouldn't you use an alias?

      Being open, with a chance of discovery at any time, would you want your name on it?

      There is no proof of ID required when submitting code!

      On the flip side, there is (yet) no evidence of a backdoor to begin with. Wouldn't the best way to shout this out to the world, be to provide proof with the offending code....?

    6. Re:What the hell? by BobMcD · · Score: 1

      No, TFA rather does make the assertion that the Scott Lowe angle is more than mere speculation. It's clearly labeled as such in the email, but the article's author apparently could only reach these two men, so he went with what he had?

  16. No BBlobs? by spyingwind · · Score: 1

    Wouldn't we be able to search the code for said backdoor? And correct me if I'm wrong, but BSD can't have binary blobs in it's code.

    --
    GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation. Social exper
    1. Re:No BBlobs? by satuon · · Score: 1

      Are you sure this means the backdoor is obvious? Like "if user == CIA then give_full_root_rights" code snippet lying somewhere?

    2. Re:No BBlobs? by Lumpy · · Score: 5, Interesting

      You dont realize how it is possible to hide evil code in front of someone's face..

      http://underhanded.xcott.com/

      go there and read, look at the winning and runner up entries... If you are a competent coder you can hide things right in front of someone and they will not spot it. It's scary as hell what some of these guys can do.

      --
      Do not look at laser with remaining good eye.
    3. Re:No BBlobs? by ray-auch · · Score: 1

      The allegation is inclusion of a side-channel in the crypto algorithm for leakage of key bits.

      If you know about crypto coding, you'll know instantly why that would be easy to hide and hard to find.

      If you don't, then any explanation is likely to be as much gibberish to you as the code would be.

    4. Re:No BBlobs? by 0123456 · · Score: 2

      The allegation is inclusion of a side-channel in the crypto algorithm for leakage of key bits.

      If you know about crypto coding, you'll know instantly why that would be easy to hide and hard to find.

      IPSEC is a well-documented standard: you can't just stick 'random numbers' which happen to contain parts of the key in the data stream as you could with some home-grown crypto system. The fact that it is a standard which has to interoperate with other implementations of the standard eliminates most of the usual methods of deliberately leaking keys.

      Certainly there could be deliberate timing effects, etc, but everyone these days should be using crypto implementations which protect against such things.

    5. Re:No BBlobs? by ifrag · · Score: 1

      If you are a competent coder you can hide things right in front of someone and they will not spot it. It's scary as hell what some of these guys can do.

      Which is why I think the best solution would be to rewrite the module from scratch and then do the audit on that version of it. Preferably developed by people who have never touched that part prior and written to spec without referencing the original code. After all, this is probably the most paranoid group in all of open source. Although speculation of a potential exploit might not be enough to drive all that.

      The whole thing does smell very fishy though.

      --
      Fear is the mind killer.
    6. Re:No BBlobs? by mzs · · Score: 1

      padding, back then it was random in OpenBSD, hard to verify, never looked at by software. Now it's speced in a verifiable manner. Either nobody knew or nobody was forth coming with the information that it was a useful side channel back then.

    7. Re:No BBlobs? by 0123456 · · Score: 1

      Does IPSEC really allow random padding? If so, the design is even worse than I imagined... I thought people figured out that non-deterministic padding was bad well over 10 years ago.

      However, if i's padded pre-encryption it's far less useful for an attacker since either it would have to somehow leak key bits into the encrypted data (which would require code that was obviously monumentally broken) or it would only leak key information to the system on the other end of the IPSEC link.

    8. Re:No BBlobs? by snowgirl · · Score: 1

      If you are a competent coder you can hide things right in front of someone and they will not spot it. It's scary as hell what some of these guys can do.

      If you're a competent coder you can make what looks like obvious mistakes that any proper editor should be able to distinguish as an error. (The top two runner ups on that page are obvious coding errors that any code review should pick up. The third is something that testing and a good code review should catch.)

      Now, all of that said, I had a hojillion code reviews working for A Very Large Multinational Computer Operating System Company that came back with the only comment being: "looks good". I caught at least one or two horrible bugs that any code review should have caught while doing my own my own code reviews after their code reviews.

      However, all of that said, the first two "winners" are of a coding level that they would never be accepted into the OpenBSD core. The third is a bit iffy, I can't speak to the specifics of how good OpenBSD code review process is... however the switching of an inequality would trigger major issues, and heaven forbid if you tried to use _snprintf() in a macro with the OpenBSD folks... Theo would hunt you down and spear you with your own buffer overflow...

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    9. Re:No BBlobs? by clone52431 · · Score: 1

      Unfortunately that seems to be deserted... I submitted an entry to “this year’s” contest, almost a year ago, and haven’t heard anything. Granted, the 2008 contest results weren’t posted until mid-October of ’09, but even by that (rather lenient) standard the 2009 contest’s results are a few months over-due. Maybe I’ll fire him an e-mail and see if he’s still planning on getting results posted.

      My contest entry used a deliberately flawed algorithm which fails in a certain case, resulting in the suitcase disappearing off the grid entirely. I kinda liked it, though I’m curious what methods other people might have used.

      --
      Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
    10. Re:No BBlobs? by garompeta · · Score: 1
      As TheRaven64 said:

      Regular code audits increase the probability that a backdoor would be found, but they don't guarantee it. That's why this is sucheffective FUD: it's basically impossible to prove that it's not true

    11. Re:No BBlobs? by BobMcD · · Score: 1

      Certainly there could be deliberate timing effects, etc, but everyone these days should be using crypto implementations which protect against such things.

      This alone is enough to warrant research into the matter. Admittedly we may be fine, security-wise, for today, but what of the last ten years and/or what about tomorrow? The alleged behavior, in my view, is a lot more interesting than the actual impact.

    12. Re:No BBlobs? by swilver · · Score: 1

      I was not really that impressed by the examples -- I expected something much more sneaky. All of those would easily be caught by writing proper unit tests.

      Place 3: Increases file size (easy check)
      Place 2: Does not zero out (easy check)
      Place 1: Uses ASCII format, would not survive conversion to binary. Any unit test against this would probably expect '0', not '00' or '000' and thus would fail.

    13. Re:No BBlobs? by mzs · · Score: 1

      It's more like '03 it became recognized more widely, since I changed jobs Dec '02, and shortly after that I heard about this idea. I remember thinking, "Oops," cause of where I had worked before and how clever we had thought we had been avoiding timing attacks which had been the previous clever trick. The best idea then was to use strong random data to pad with, and we did. Of course that was really hard to check if it was simply random padding if you wanted to verify it, to make sure nothing was being leaked there for example.

      In any case the IPSEC specs were then later changed to recommend defined padding, and yes the padding I am referring to you would not need the keys before hand to look at. Of course there are lots of other ways to leak things, like timing which you mentioned, or the way you break-up packets, or where/when you use options, etc. All those would be harder to hide in the code though.

      FWIW, I'm thinking these claims made by Perry are a load of crap, but that's just my opinion.

  17. Theo didn't make the claim by 7x7 · · Score: 4, Insightful

    Someone sent an email to Theo making the claim. Theo put it on the internet. Now it's true.

    1. Re:Theo didn't make the claim by interval1066 · · Score: 2

      It looks to me like de Raadt received an email from this Perry saying that he had some kind of NDA with the FBI that was part of a project the FBI hired Perry to do to add a back door to the OBSD ipsec stack, and the tone *seems* to be "ha ha ha, I screwed you" a little bit, shown by his comment about OBSD's DARPA funding. de Raadt isn't confirming or denying, he's simply saying "Look, this asshole is making claims." Claims that should be easily refuted if the OBSD stack is as heavily audited as the group claims.

      --
      Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
    2. Re:Theo didn't make the claim by John+Hasler · · Score: 1

      Is the auditing being done by a completely seperate, unrelated, and independent group?

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    3. Re:Theo didn't make the claim by interval1066 · · Score: 1

      I don't know, there's probably more detail at openbsd.org.

      --
      Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
    4. Re:Theo didn't make the claim by lysdexia · · Score: 1

      I agree. I thought Mr. Perry's email seemed fairly apologetic when read as a whole. The comment vis. DARPA funding seemed a bit gossipy, but not maliciously directed at Theo.

  18. Slashdot: "News" by BitHive · · Score: 2

    Because it's too much trouble to quote or reproduce Theo's brief email and people wouldn't know what to make of it anyway.

  19. Re:Show me the code. by just_another_sean · · Score: 1

    Here you go: The Code.

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  20. Bump by AdmV0rl0n · · Score: 5, Interesting

    The raw and cold truth is that contributors to all the open OSs can't really be vetted. Not in a meaningful way. And the number of people who are deep low level 'hackers' capable of writing the code is relatively small. The numbers able to code audit to a level of examination are even fewer. So yes, the code is open, the code is visible, the code can and could be audited. But here is the thing, being auditable is not the same as being audited. And personally, I would not be shocked if a full audit was run if something might be found.

    That being said, this is one step better than closed source, where some of the above is not possible or viable, and in cases where money crosses palms, may in fact be unwanted.

    Further to this though, I personally don't expect government to simply roll over and die. I expect them to take steps to try and stay one step ahead of bad things, and the relaxing of technology limits has benefitted people across the world, even if I were to make a case that the cost is that at the point of a pyramid - the goves can hunt down the world culprits and suspects. In some cases - releasing the tech in fact has your enemy using that tech after some time and you get to tap into it.

    At least its an interesting story :)

    --
    We`re all equal .. Just some of us are less equal than others.
    1. Re:Bump by Xemu · · Score: 2

      The raw and cold truth is that contributors to all the open OSs can't really be vetted. Not in a meaningful way.

      Indeed. However, the raw truth is that open source contributions can be vetted in a meaningful way.

      Don't fool yourself into believing that there are no backdoors in closed-source software.

      --
      Tell your friends about xenu.net
    2. Re:Bump by snowgirl · · Score: 3, Interesting

      So yes, the code is open, the code is visible, the code can and could be audited. But here is the thing, being auditable is not the same as being audited.

      Except this is OpenBSD we're talking about, where code audits happen frequently and often.

      And personally, I would not be shocked if a full audit was run if something might be found.

      A full audit would be run repeatedly over the course of this coming year even if this accusation had not come out. After all, we are talking about OpenBSD.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    3. Re:Bump by AdmV0rl0n · · Score: 1

      You obviously failed to read my first comment. Go back, you'll see the part (*I*) spoke about closed source.

      --
      We`re all equal .. Just some of us are less equal than others.
    4. Re:Bump by BobMcD · · Score: 1

      So yes, the code is open, the code is visible, the code can and could be audited. But here is the thing, being auditable is not the same as being audited.

      Except this is OpenBSD we're talking about, where code audits happen frequently and often.

      And personally, I would not be shocked if a full audit was run if something might be found.

      A full audit would be run repeatedly over the course of this coming year even if this accusation had not come out. After all, we are talking about OpenBSD.

      Consider this - if this backdoor existed then or exists today, what would that say about the process?

    5. Re:Bump by rev0lt · · Score: 1

      Not much time ago, it passed at least a full year between rumours of an actual ssh exploit and the disclosure of the vulnerability and release of some poc code. Trusting OpenBSD just because is OpenBSD is nonsense. Crypto is nontrivial, and protocols itself are quite complex (and IPSEC is no walk in the park), so it may be possible that a developer had implemented some protocol in such a way that it woud be vulnerable to a specific kind of attack, without anybody noticing. It gives me some satisfaction that the OpenBSD team learned from past mistakes, and this time - even without evidence, and it may well be a hoax - Theo decided to make this public. And yes, I'm an OpenBSD user.

    6. Re:Bump by rev0lt · · Score: 1

      The same thing it says when they sort out bugs in ancient blocks of code. That auditing is a continuous process, not a goal.

  21. leaks by Jimpqfly · · Score: 1

    They can deny: in a couple of days we'll find evidences on wikileaks...

  22. Theo did not make the claim.. by TheNinjaroach · · Score: 2

    He simply released the email that was sent to him.

    --
    I went to eat some animal crackers and the box said, "Do not eat if seal is broken." I opened the box and sure enough..
  23. Smells like FUD to me by ilovecheese · · Score: 1

    What really gets me, is this is all open sourced code. This means that a code audit would find this so-called back door, yes? I seriously doubt this so-called claim.

    1. Re:Smells like FUD to me by Anonymous Coward · · Score: 1
    2. Re:Smells like FUD to me by TheRaven64 · · Score: 5, Insightful

      This means that a code audit would find this so-called back door, yes?

      Nope. OpenBSD is audited, but the auditors are human (well, some aren't, but they can only spot categories of bug that are well documented). The code is not formally, mathematically verified (doing so for nontrivial C code is basically impossible), so there's always the possibility of a bug and, as the OpenBSD team says, the only difference between a bug and a vulnerability is the intelligence of the attacker.

      Regular code audits increase the probability that a backdoor would be found, but they don't guarantee it. That's why this is such effective FUD: it's basically impossible to prove that it's not true.

      --
      I am TheRaven on Soylent News
  24. Re:Backdoor? But it's open-source! by ledow · · Score: 1

    What backdoor? Nobody has found ANYTHING yet. They just have a rumour, duly propogated onwards because of its *potential* security applications, that someone may have once been paid to do such a thing. Doesn't mean it's true, that they succeeded, or that it hasn't been removed since.

    It's impossible to prove something *isn't* there, of course, but it would be a cinch to prove it *was*. Nobody has yet stepped forward with anything even approaching a slight vulnerability in their IPSec implementation that isn't well documented and patched already (or even suspected of being planted maliciously). That's the beauty of OS - we can go back and check and see and hold people accountable, and YOU can take a look if you don't believe us, or think we're in league with the FBI. There's absolutely *nothing* to stop you. Now go ask about proprietry software vendors and *their* relationships with the FBI and see how many answers you get.

    And I don't even care about BSD - I've only ever used it once, and Linux has a *completely* independent IPSec implementation made by completely separate people. If it's a concern for you, audit the code, or pay someone to do it. Chances are you'll never be *allowed* to audit similar code from, say, Microsoft and certainly not allowed to publish your findings if you *did* find a backdoor in it. In the OS world, though, we publish even potential RUMOURS of a possible hole, so that you can be the judge and not anyone else.

  25. Unlikely... by JustNiz · · Score: 1

    It seems unlikely that someone could hide one or more backdoors in such a ubiquitous piece of code without _anyone_ else ever spotting it.

    It also seems unlikely because Perry didn't share actual technical details of the backdoor(s) so their existence can be proven. Surely when making such a radical claim its just human nature to also justify it with all the evidence you have.

    1. Re:Unlikely... by GooberToo · · Score: 1

      Case in point, I literally just spotted a bug in python's socket recv call (as of yet unreported) which leaks memory given the right error conditions. The code hasn't been modified for seven months and the file has existed for many, many years. The only reason I spotted it is because I was looking for very specific but unrelated behavior. Regardless, subtle errors and by association, malicious code, can easily exist for very long times, even surviving multiple code reviews.

      The most important thing to remember about the human brain is, it ALWAYS wants to see what it wants to see.

    2. Re:Unlikely... by AHuxley · · Score: 1

      Open or closed, knowing one good (not really looked for over life of the product) error or more can be the key.
      Injected by design or offered as part of a deal.

      --
      Domestic spying is now "Benign Information Gathering"
  26. Is (was) the FBI ever working w/ OpenBSD -AT ALL-? by clone52431 · · Score: 1

    If so, where’s this NDA that Theo claims just expired? Surely he didn’t run it through the shredder already.

    --
    Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
  27. Re:Oh come on by ledow · · Score: 3, Insightful

    Funnily, that's exactly what happened to me - I wondered what people were talking about when they said it was a dupe. This is the only website I've ever had to block a submitter on, and kdawson the ONLY author I've ever had to block on any website because every submission I read from them annoyed me or was blatantly complete bollocks.

  28. Re:Is (was) the FBI ever working w/ OpenBSD -AT AL by clone52431 · · Score: 1

    Correction, Gregory Perry claimed to have an NDA with the FBI. Theo was just the messenger. Damn, this is confusing...

    --
    Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
  29. Re:Oh come on by alphax45 · · Score: 1

    You made me choke on my lunch!

    --
    K Man
  30. Re:Oh come on by LWATCDR · · Score: 1

    So slashdot gets a twofor.

    BTW the Indian extremists have been infiltrating Microsoft for years and have places many back doors into Windows so they can shutdown all our systems. Their main target is the thought control experiments based in Montauk NY at the secret underground base their. They are hoping that they can remotely activate it and then while we are under their control gain access to the secret base under the new Denver Airport.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  31. Re:Oh come on by clone52431 · · Score: 1

    No, I don’t think so, because they do sometimes edit the stories. I know they edited one that I posted, they converted it from a logically divided 3-paragraph submission into a single glob of text, just like any other story.

    --
    Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
  32. This is why I only use windows. by Anonymous Coward · · Score: 2, Funny

    I only use OSes I can trust!

    1. Re:This is why I only use windows. by HiThere · · Score: 1

      Sorry, but I can't figure out whether that's a joke, you're a troll, or you're really that stupid. (I figure that if you're on /., you can't really be too ignorant to just be uninformed.)

      My bet is that it's a joke, but I sure wish the odds were better.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  33. Oh yeah - because they'd admit it... by moxley · · Score: 1

    Like they'd come out and admit it if it IS true.

  34. Re:Oh come on by eln · · Score: 3, Funny

    Nonsense. Nobody working for this site has ever been a good enough perl coder to pull that off.

  35. Re:Oh come on by elrous0 · · Score: 2

    Kdawson is just an internet myth, long ago disproven by snopes.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
  36. Re:Oh come on by HermMunster · · Score: 1

    Have these two deniers stated whether they are under NDA still? Why would they admit to it when doing so would brand them?

    Even though I think it is tough to miss something like that in the code it is still possible. Everyone should look to ensure that removal is performed.

    If they could do that then they'd do it in Windows. Windows is closed source and easily altered. If it is verified in BSD you can be guaranteed it's in Windows.

    Though this is likely true (that the code is there), it is difficult for me to see them having the programming skills back then to write something so sophisticated that it would go undetected for over a decade.

    Why was the "leaker" under NDA to begin with?

    --
    You can lead a man with reason but you can't make him think.
  37. time to call Ponderosa Puff by Spy+Handler · · Score: 1

    and tan his hide!

  38. Re:Oh come on by mr.dne · · Score: 2

    I've been following slashdot for over 10 years and I finally registered an account just a few weeks ago. Why? Because I got so sick of kdawson's inflammatory Fox-news-esque junk articles that I finally decided to register just for the sole purpose of kill-filing him.

  39. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  40. Re:Oh come on by RDW · · Score: 1

    'This is the only website I've ever had to block a submitter on, and kdawson the ONLY author I've ever had to block on any website because every submission I read from them annoyed me or was blatantly complete bollocks.'

    You must be new here:

    http://www.theobvious.com/archive/1999/03/25.html

  41. Re:Oh come on by Quiet_Desperation · · Score: 1

    It's worse than you imagine. It's a Visual Basic program.

  42. Re:Oh come on by aztektum · · Score: 1

    And then there is this post from CmdrTaco that utterly misinterprets what happened.

    Why do I come here? I'm slowly coming less and less and shit like this doesn't help.

    --
    :: aztek ::
    No sig for you!!
  43. Re:Oh come on by Jay+Tarbox · · Score: 1

    Whatever happened to John Katz?

  44. Re:Oh come on by Farmer+Tim · · Score: 2

    Can't say I have. The last joke I made about bestial dwarf porn got modded up pretty quickly.

    --
    Blank until /. makes another boneheaded UI decision.
  45. lies, damn lies and statistics by slick7 · · Score: 1

    Both denied working with the FBI.
    But did they deny working for the FBI, directly or indirectly?

    --
    The mind conceives, the body achieves, the spirit manifests.
  46. Re:Oh come on by Thud457 · · Score: 1

    I miss JonKaz.

    Wait, no I don't.


    Although I'd like to see a follow-up on how Junis is faring in Afghanistan these days. /. really should have a telethon to upgrade him to an Amiga.

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

  47. Re:Oh come on by asvravi · · Score: 1

    Well somebody did.. and named the script kdawson.

  48. Re:Oh come on by Farmer+Tim · · Score: 1

    I thought blonde socialites were defenceless pets. I certainly haven't seen a practical reason for their domestication...

    --
    Blank until /. makes another boneheaded UI decision.
  49. Re:Not BSD coder by BatGnat · · Score: 1

    was it FreeBSD then?

  50. "Shocking Claim" !== Theo DeRaadt. Misleading. by lysdexia · · Score: 1

    Theo DeRaadt did not make any claims, he merely released an email from a fellow who claims to have been involved in placing backdoor code into ipsec. The original sender has not denied anything about the content of the message and it has appeared (afact) unedited.

    I doubt if this will stave off the usual Berate DeRaadt Party. I believe that he has handled this with a minimum of B.S. and is allowing the social situation to resolve without adding the measure of vitriol he would be justified in throwing.

  51. Re:Oh come on by damien_kane · · Score: 1

    I believe there's a law against releasing defenceless pets into the wild.

    That's why so many Chihuahuas keep blonde socialites.

    There, ftfy

  52. Re:Anyone else think of... by lysdexia · · Score: 1

    Only since the first time I heard it. :-)

  53. Re:Backdoor? But it's open-source! by lysdexia · · Score: 1

    True. I'm sure people are combing the commits from that era pretty heavily as we write.

  54. Re:Oh come on by Gilmoure · · Score: 1

    I thought /. was a labor of love. How can you let go someone who works for free?

    --
    I drank what? -- Socrates
  55. Re:Is (was) the FBI ever working w/ OpenBSD -AT AL by lysdexia · · Score: 1

    Good catch, and good point. :-) I'm with holding judgment on the NDA until it is released to the world. Mr. Perry may not be legally able to do that, though.

  56. Re:The email chain is a bit long by lysdexia · · Score: 1

    Someone claiming to be Gregory Perry has confirmed sending the email in numerous articles linked to in this and the previous post.

    See? Now we are just as sure as we were before.

  57. Re:Oh come on by Richard+Steiner · · Score: 1

    Maybe we can induce his return?

    John Katz.

    John Katz.

    John Katz.

    *waiting*

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  58. Re:Oh come on by Gilmoure · · Score: 1

    I think it's spelled J - O - N.

    But I'm not going to invoke him. I'll just watch old reruns of The Critic and that other cartoon that came on after it.

    --
    I drank what? -- Socrates
  59. Re:Oh come on by Gilmoure · · Score: 1

    Regular bollocks, dog bollocks or ex-gf has stomped all over my bollocks?

    --
    I drank what? -- Socrates
  60. Re:Oh come on by Gilmoure · · Score: 1

    You have a high UID. Heh!

    --
    I drank what? -- Socrates
  61. Re:Show me the code. by BobMcD · · Score: 1

    Here you go: The Code.

    It looks like you trimmed your link. This goes to the root of the entire CSV. We'd want to see the specific code in the allegation, as it was submitted back in 2000/2001. Got THAT link?

  62. Re:Oh come on by Darinbob · · Score: 1

    Wait.. we can block kdawson??

  63. Title is deceptive, not coders by George_Ou · · Score: 1

    The claim about Scott Lowe (which one never specified) was that he was on the FBI's dole to write how to implement OpenBSD based VPN VMware tutorials. Writing tutorials doesn't make him an OpenBSD coder. The claim was that "Jason Wright and others" were the ones who inserted the backdoor into the source code of OpenBSD. I haven't heard any refutation from Jason Wright and the story doesn't even claim that.

    1. Re:Title is deceptive, not coders by funky+womble · · Score: 1
    2. Re:Title is deceptive, not coders by George_Ou · · Score: 1

      Thank you for link.

    3. Re:Title is deceptive, not coders by John+Hasler · · Score: 1

      That's a denial, not a refutation. While I am inclined to believe Jason, a refutation would contain proof (or at least strong evidence) of the falsehood of the allegation. That is something that is going to take time to produce.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  64. Re:Oh come on by BitZtream · · Score: 1

    Heh, funny part is, as soon as I saw the original story, noticed who posted it, I instantly determined it to not be true.

    From that point I went and looked deeper and find it highly unlikely that much of the story as currently told is true.

    It looks more to me like the email from Gregory Perry is either spoofed, or that he has an agenda.

    The 'agenda' part stems from the fact that he's the 'CEO' of 'GoVirtual Education' a company selling VMware training ... and he happens to be taking pop shots at a guy who promotes using OpenBSD VMs ...

    I'm sure in the end, this will turn out to be just another silly thing that isn't true and is exactly why I blocked kdawson in the first place.

    It would seem that others at slashdot seem to realize no one reads the retarded crap he approves and have taken it on themselves to post followups to link back to his stories or posting submissions from him directly.

    Dear slashdot, please give me a way to not see anything that in any way relates to kdawson or timothy, it always turns out to be wrong, most of the time its unbelievably wrong.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  65. Bad Summary by atomic-penguin · · Score: 1
    Scott Lowe, the named person in the e-mail was never accused of being a BSD coder/developer, in the original e-mail. If you read carefully, he was accused of advocating (while allegedly on the payroll of the FBI) the use of OpenBSD as a VPN/firewall solution specifically in VMware environments. No surprise that he writes books or tutorials for VMware since he, in fact, works for EMC. The original paragraph from the e-mail accusing involvement of Scott Lowe. Facts disputed by Scott Lowe appear in italic, below. Important note: at no point in the original e-mail was Scott Lowe accused of being an OpenBSD coder/developer, or committing compromised code to the OpenBSD project.

    This is also why several inside FBI folks have been recently advocating the use of OpenBSD for VPN and firewalling implementations in virtualized environments, for example Scott Lowe is a well respected author in virtualization circles who also happens top (sic) be on the FBI payroll, and who has also recently published several tutorials for the use of OpenBSD VMs in enterprise VMware vSphere deployments.

    Jason Wright, on the other hand was the accused coder. Jason Wright has not issued any public statement on the matter, and the linked article only makes a slight mention of him.

    --
    /^([Ss]ame [Bb]at (time, |channel.)){2}$/
  66. Actually by br00tus · · Score: 1

    You talk about a "mailing list posting by one person" and a "mailing list author [who] was making a total reckless claim". But there is no mailing list author, a private e-mail was sent to Theo who decided to make it public on the mailing list. One reason for the lack of proof etc. is Theo stated he had no desire to speak to Greg about this, and Theo made it immediately.

    You also say this is by "some random person" but it is not, it is someone who was involved in AFAIK financing this part of OpenBSD development, and who worked at the same company as other people who have committed code to OpenBSD. A person posting anonymously here is "some random person", someone with that type of involvement with the various persons is NOT some "random person."

    Posting this on Slashdot is not gross negligence at all, I am much happier to be aware of this story than not aware of it. It does not seem far-fetched to me either - it seems like DES - algorithms are put out by the government, or by government contractors which are safe for most people, but which the government can still decode. Did DES come with big warning labels, "hey, the government can decrypt this but most people can't". If DES had an unlabeled "backdoor" (of sorts), why is it so surprising there might be a backdoor of sorts here, even if it is only a few changes that make decryption of this stuff easier for the government?

    On the negligence angle again, that would be more on Theo's end than anything. I'm glad Theo made this public, but I think he could have been a little more subtle, removing everyone's name from it for one thing. But that is on him, not Slashdot.

  67. Re:Show me the code. by just_another_sean · · Score: 1

    Is this better?

    --
    Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  68. Re:Show me the code. by BobMcD · · Score: 1

    Yep...

  69. Re:Oh come on by John+Hasler · · Score: 1

    Are subscribers also able to killfile users? If so I just might subscribe.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  70. No ownership of ideas. No rights. by gottabeme · · Score: 1

    Please, don't add to the disgusting, overused mess that is contemporary copyright doctrine by misapplying it to private correspondence! It's arguments like yours that make me wonder if we really would be better off overall with no copyright whatsoever.

    No one should be able to own an idea. It's that simple. The only reason we have the concept of owning ideas is because of technology that allows mass reproduction and the greedy desires to squeeze every last cent out of something, and to prevent others from deriving any benefit from anything you do without paying you for it.

    I also think it's dangerous and foolish to start tossing around the word "rights." The only rights anyone really has in this country are spelled out in the Constitution and the Bill of Rights. I may not have a "right" to copy and forward and publish the email you send me, but you don't have a "right" to stop me from doing so, either. If you don't trust me to abide by your wishes, don't send me the email. You have the "right" to not email me.

    --
    "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
  71. Refuting might be difficult by gottabeme · · Score: 1

    Refuting the claims by auditing the code might not be so simple. Read the thread started by de Raadt's email for details.

    --
    "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
  72. A likely story by athlon02 · · Score: 1

    This person denies they put in backdoor code for the FBI... a likely story! That's just what a person working secretly for the FBI would say. And next he'll claim he's not a BSD coder too! He's guilty, guilty I say!

    Seriously, until the code has been fully audited and results released, the original blurb on this is enough, I don't need several stories in a day on it. This kind of "reporting" reminds me of an incident that newscasters reported and kept updating every 30 seconds as though something amazing was going to happen any second.

  73. Re:No ownership of ideas. No rights. by DamonHD · · Score: 1

    a) Copyright is there and the Berne convention applies more or less world-wide.

    b) The Constitution and Bill of Rights *does not* apply worldwide and I am not in the US.

    So, by treaty, I believe I have more "rights" to stop you publishing the verbatim text of my private emails to you than you have to publish them.

    Yes, copyright is messy, and I'd prefer not to use it, but it applies cross border.

    And yes I'm not claiming to be able to stop you forwarding "ideas", I'm talking about forwarding my text as is.

    Rgds

    Damon

    --
    http://m.earth.org.uk/
  74. Re:No ownership of ideas. No rights. by gottabeme · · Score: 1

    I suppose we'll just have to disagree, then.

    I must say, though, the more stupid copyright issues I read about, and the more I think about it, the more I think the very idea that anyone should be able to own a collection of letters and words borders on absurdity. Every single creative work there is has borrowed from thousands of years of history, language, folklore, legend, myth, collective cultural consciousnesses, etc. Originality is a myth--only God was truly original. And so, since we all owe something to those who have come before us, without which we couldn't have created what we've created, I think it's bordering on morally wrong to try to take exclusive ownership of an idea or collection of ideas, because in the end it's hypocritical.

    --
    "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
  75. of course they will deny! by Syobon · · Score: 1

    -IF it's in their contract with US government, and you can audit the code for ever, the backdoor will never show itself, think about complex mathematic algorithms that, let's say by the delay in processing can say that a bit is 0 or 1.

  76. Re:Oh come on by Thinboy00 · · Score: 1

    Wait.. we can block kdawson??

    /me checks

    Yes!

    --
    $ make available
  77. Open BSD an acronym for by HongPong · · Score: 1

    Open Bothersome Side Door .