Slashdot Mirror


Theo de Raadt Discusses OpenBSD and Beyond

emil writes to tell us that NewsForge (Slashdot Sister Site) is running an interview with OpenBSD project leader Theo de Raadt. In the interview Theo explores the upcoming release of OpenBSD 3.9, continuing financial difficulties, and some of the tension between the OpenBSD team and other businesses that some feel are taking advantage of the free software without giving anything back. In related news the Jem Report has an interesting writeup that expounds on widespread difficulties that could be faced if the OpenBSD project continues its downward spiral because of their parallel development of OpenSSH.

78 of 476 comments (clear)

  1. stay on topic by r00t · · Score: 3, Funny

    Finally, for real, today's topic is: BSD is dying

    All other posts are off-topic. Enjoy!

  2. Hmm... by Eightyford · · Score: 2, Insightful

    ...that some feel are taking advantage of the free software without giving anything back.

    Damn. I wonder if there was anything they could have done about that?

    1. Re:Hmm... by dtfinch · · Score: 4, Informative

      I'm pretty sure he's heard of it. While they do appreciate source code contributions, what they're really asking now for is money.

    2. Re:Hmm... by AHumbleOpinion · · Score: 5, Informative

      ...that some feel are taking advantage of the free software without giving anything back.

      Damn. I wonder if there was anything they could have done about that?


      No there wasn't, BSD as in Berkeley Software Distribution, as in University of California Berkeley, as in "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved.", as in paid for by California taxpayers including corporations and individuals who should not be denied access to what they paid for.

      BTW, you shouldn't confuse BSD with a very talented but potentially mismanaged team that has a tendency to piss off lucrative sources of income.

    3. Re:Hmm... by arivanov · · Score: 4, Informative

      Not really applicable.

      They started with a fork of the NetBSD codebase and maintained compatibility for a long while. Many drivers in the Net/OpenBSD tree used to be ifdef-ed for specific OS related parts. In fact one of the reason for OpenBSD to survive for so long especially on obscure architectures has been the fact that it used to rely heavily on Net for low level hardware specific code (disclaimer - I do not know if this is still the case as I have not looked at their source since 3.3).

      As a result GPL-ing is not an option. Your codebase is heavily dependant on somebody's else's codebase which is BSD.

      As far as the financial difficulties, all business and businesslike entities using GPL rely on support, custom code and consulting for their day to day living expenses. You do not get that money if you have this attitude:
      http://www.securityfocus.com/archive/1/428749/30/9 0/threaded. This is just one fresh example (this week).

      Another essential factor is that if you write software in the real world you have to go out of your ivory tower on a daily basis and check what your competitors doing. OpenBSD tends to believe its own PR about their security prowess and does not follow Linux, FreeBSD and other OS development as much as it should. One example for this is how it missed the appearance of hardware RNG in AMD hardware for several years. They simply did not know it is there (I actually pointed it to Theo myself a year ago). I bet that they have missed other stuff in a similar fashion as well.

      Frankly, the days when Open Source OS projects were PFY jobs and flaming each other out of existence on mailing lists was business as usual are long gone.

      Time to grow up or face the dark stairway down down and down towards oblivion.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    4. Re:Hmm... by 0racle · · Score: 2, Informative

      They don't like the GPL and are currently removing GPL only licensed code from the base install. The GPL is not an option for OpenBSD.

      --
      "I use a Mac because I'm just better than you are."
    5. Re:Hmm... by IgnoramusMaximus · · Score: 3, Insightful
      They don't like the GPL and are currently removing GPL only licensed code from the base install. The GPL is not an option for OpenBSD.

      Subsequently, their moaning about how their self-inflicted mortal wounds hurt horribly is going to rightfully fall on deaf ears, if they are lucky, or will become a butt of jokes, if they are not.

      This is what happens if someone is given good advice not to drive their car off the road and into a bog and which they derisively reject and proceed at "what can possibly happen?"-speed into the mud. Following which they sit on top of their sinking vehicle, far into the swamp, waving frantically and complaining loudly about "selfish" people who fail to stop to pull them out of there. So that they can ignore good advice, as soon as rescued, derisively, again.

      I say onto Theo: Tough Cookies! You made your bed, you sleep in it! Perhaps placing product placements into the BSD code or performing in a clown outfit at conferences will bring the required revenue, now that the commercial interests do what you have always encouraged them to do: take, take and take ... whatever they can get in return for as least as possible. Its called "business", Theo. Look it up sometime.

    6. Re:Hmm... by Quantum+Fizz · · Score: 2, Interesting
      As a result GPL-ing is not an option. Your codebase is heavily dependant on somebody's else's codebase which is BSD.

      Dumb question, but if you can take BSD-licensed open-source code and put it in closed-source code, why can't you take the same code and GPL it (maybe make slight trivial modifications to make the software unique before GPL'ing)? I mean, it would most likely piss the BSD team off if someone did this, but legally speaking, is there a reason it cannot be done?

    7. Re:Hmm... by jbailey999 · · Score: 3, Funny

      GPL people are cool. I like to make copies of them. The only problem is that everytime I give one a way, I have to give the damned cloning formula away...

    8. Re:Hmm... by kv9 · · Score: 2, Funny

      nice troll. however i do believe that he wants money to support the project and not his drinking habits.

    9. Re:Hmm... by rhavenn · · Score: 3, Insightful

      I don't get why people dump on Theo all the time. Yeah, he really could use a PR manager at times, but all the threads I've read he usually is right or standing up to what he believes is right. Can Theo be a dick about it? Yeah. Can Linus and Stallman be dicks about the kernel and the GPL? Yeah. Get over it and maybe send them some money for this OpenSSH thing we all use.

    10. Re:Hmm... by Doctor+Memory · · Score: 2, Insightful

      you have this firmly held belief that the rest of the world owes you something?

      No, his point is that he's not being paid for this, so people should stop treating him like an employee. Part of the freedom of writing FOSS code is that you don't have to bend over backwards to accomodate people, because they aren't paying customers. If somebody thinks some software I wrote should have some feature, or should work in a certain way, and whines because it doesn't, I can tell them to take a hike, because I provide the software at my whim and convenience. If I'm a good, conscientious developer, then I'll listen and add their request to the "future directions" list, but I certainly don't have a mandate to do so.

      To paraphrase Al Capone, "You can get better support with polite e-mail and a $100 check than with polite e-mail alone".

      --
      Just junk food for thought...
  3. SunSSH by dtfinch · · Score: 2, Interesting

    "I will say it here -- if an OpenSSH hole is found that applies to SunSSH, Sun will not be informed. Or maybe that has happened already." - Theo de Raadt

    I'm sure they'll find out when everyone else does.

  4. what a whiner by penguin-collective · · Score: 2, Insightful

    Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products.

    What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.

    Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.

    For our work on OpenSSH, companies using OpenSSH have never given us a cent. What about companies that incorporate OpenSSH directly into their products, saving themselves millions of dollars?

    No, they haven't been saving themselves "millions of dollars". If OpenSSH didn't exist, people would implement some other free ssh client or switch to a different standard.

    If you release something under a FOSS license, figure out your business model beforehand. Of course, Theo actually did: his work on BSD has given him plenty of exposure and celebrity status, which many would consider ample reward for his work, and something he wouldn't have gotten if he had founded a small software company instead. And I'm sure he could (or could have) translated this into consulting opportunities and other business, without even changing the license on anything. But, like many celebrities, it's just never enough.

    1. Re:what a whiner by Schraegstrichpunkt · · Score: 3, Insightful
      Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products.

      What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.

      That part wasn't written by Theo, as far as I can tell.

    2. Re:what a whiner by QuantumG · · Score: 2, Insightful

      Let's face it, the reason why Theo de Raadt can't maintain his unpaid work on OpenBSD/OpenSSH is because he's an impersonable jerk. You can't make money as a consultant if your response to everyone is just to tell them to shut the hell up. You may be able to make money from speaking tours (like RMS does) but you actually have to have enough patience and dedication to stand up deliver a talk that people who are willing to pay to hear (i.e., not talks that people give to developers). Theo reminds me of people who like to play folk music or surf all day. They run around looking for sponsors but they're not interested in putting on shows or entering competitions.

      --
      How we know is more important than what we know.
    3. Re:what a whiner by hhw · · Score: 5, Interesting

      Just because the BSD license doesn't force companies to give back, doesn't mean they can't do it anyway.

      For a business that uses OpenBSD code, it would just make good business sense to support the project at a fraction of what it would cost to develop the same code in-house. It is ridiculous that Sun wouldn't even cover the travel expenses of an OpenBSD developer to go their conference, because the value of the developer's hours would have far exceeded such travel expenses. That's just simply bad business.

      --
      http://astutehosting.com/
    4. Re:what a whiner by pherthyl · · Score: 4, Insightful

      Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.

      What are you talking about? People use OpenSSH because it's by far the best out there. Nobody is locked into using it, the specs are open, anyone can code a replacement. It's just not easy to produce something of the same quality and security as OpenSSH. People are locked into Windows because of proprietary file formats and closed source applications; how is that in any way similar to OpenSSH?

      But, like many celebrities, it's just never enough.

      Sorry. CELEBRITIES? Hmm.. yeah sure, Theo is a celebrity. I'm sure he has paparazzi knocking on his door every day.

      Sure Theo can be abrasive, but it's weird to see how gleefully people at the receiving end of his charity will attack him. It's always easy to be an armchair critic.

    5. Re:what a whiner by lintux · · Score: 4, Informative

      Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.

      Actually, it isn't. You can also use LSH or Dropbear, and for SSH clients there are even more alternatives (PuTTY is available for Linux, for example).

      This article almost makes me consider using one of them...

    6. Re:what a whiner by cyberjessy · · Score: 5, Insightful

      What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.
      Furthermore, what makes Theo think that people want to run OpenSSH? At this point, it's as entrenched as Windows--nobody has a choice.


      Dear friend, herein lies the indelible mark of your misunderstanding of the free software _Movement_, and will live on even after you are dead and gone.

      The help he is asking is pocket change for the companies which use OpenSSH. For the work done in making it compatible with major projects of those companies. __If you read the article__ you will also note how IBM sends customer complaints to the OpenSSH team. And how Sun refused to pay for travel!

      I find it painful.

      --
      Life is just a conviction.
    7. Re:what a whiner by pherthyl · · Score: 4, Insightful

      If OpenSSH didn't exist, the ssh 1.3 source would probably have been picked up by GNU and we'd have free GnuSSH, without Theo's whining.

      I'm sure you're right, it's not like we wouldn't have another SSH client, but would it be as good? The fact is that Theo and his team writes really good, really secure code. Someone who does security "for fun" is very rare and valuable. Most developers are quite naturally more interested in cool features than tedious code review.

    8. Re:what a whiner by giorgiofr · · Score: 3, Funny

      the ssh 1.3 source would probably have been picked up by GNU and we'd have free GnuSSH

      which would suddenly turn off encryption on your channel and pop up RMS's face saying "You are using this software for something *I*, his Imperial Majesty RMS, happen not to like today or maybe in the future, therefore I will stop it. I also hope your OS crashes and burns because it's not running HURD."
      Thanks, I'll keep using the *really open* OpenSSH.

      --
      Global warming is a cube.
    9. Re:what a whiner by kv9 · · Score: 2, Interesting

      it's just bad business. lately lots of companies got big on open source and seeing how SUN (and others) has openssh based products, it would be freakin common sense to give something back to the developers. "well shit, they threw all that code in the wild, we're using and profiting from it, why not drop them some dosh so we motivate them to keep up the good work, so we don't have to".

      some recent examples:

      HP donated a 20 node blade monster to the FreeBSD project last year in december "We at HP recognize the important role of FreeBSD in the Internet's global network infrastructure, and we are happy that the HP BladeSystem cluster can contribute to the on-going success of the FreeBSD Foundation"

      i was listening to a LUGRADIO episode recently and there's this propylon company which specializes in legal products, and they are the fourth largest contributor to OO.o -- nothing small either, they got like 60 devs on top of shit.

      and i'm sure the list can go on and on. so before you blame big bad theo for expecting something back from the `freeloaders' why don't you look around at what other `big bad souless companies' are doing?

      --EORant

  5. You doity raht by The+Famous+Brett+Wat · · Score: 4, Funny

    Is it just me, or does anyone else always feel the urge to pronounce "Theo de Raadt" as "Theo da Rat" with a mafia godfather style accent?

    --
    proof, n. A demonstration that a conclusion is implied by certain premises and axioms.
  6. Problem with BSD licencing by PAPPP · · Score: 4, Insightful

    This is a perfect example of the problem with BSD licencing. Under the various BSD licences, its perfectly OK to take a piece of code and sell it, either modified or exactly as found, without in any way recognising or contrubuting to the project. Run "strings c:\windows\system32\ftp.exe" on a WinXP box and you'll see a perfect example of uncredited work. At least under the GPL if someone sells an unmodified program, the project will get recognition (since it will have to remain open source, and thus the origion of the code will be obvious), and if they sell a modified version the project will get the source for the modifications back. Neither directly equates to funding, but publicity and a better code base both help to attract financial support. Both arrangements depend somewhat on the cooperation and altruism of the entity using the code for a profit, but the GPL isn't quite so hopelessly naive.

    1. Re:Problem with BSD licencing by Darby · · Score: 4, Interesting

      I've mentioned this in another post but be careful with words like "contributing". As California corporations and taxpayers companies like Apple and SCO paid for BSD's development. Apple have every moral and ethical right to use it.

      They paid for ancient BSD development. However after the court cases were over, that went away.
      They have every *legal* right to use it.
      They have an ethical responsibility to contribute but this is in no way required.
      Morality is individual, so were you talking about a person it would be their choice as to what their morality is. As you're discussing corporations, they inherently and as required by law are entirely amoral.

      This is certainly about as clear a demonstration as you can find of the difference between the BSD license and the GPL, but other than that, which wasn't explicitly in there, there really isn't anything to your post.

      Is Theo justified in calling the people who used his code without giving anything back asshats? Absolutely.
      Can he force them to? Absolutely not.

      That's the license he chose and he's well aware of the ramifications.

      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature.
      The optomists are losing badly.

    2. Re:Problem with BSD licencing by AHumbleOpinion · · Score: 2, Insightful

      They paid for ancient BSD development. However after the court cases were over, that went away. They have every *legal* right to use it. They have an ethical responsibility to contribute but this is in no way required.

      It's not so ancient: "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved". An this code remains at the heart of the *BSD projects.

      Morality is individual, so were you talking about a person it would be their choice as to what their morality is. As you're discussing corporations, they inherently and as required by law are entirely amoral.

      Completely false. They are permitted by law to be amoral in some respect, they are not required to be. A corporation can choose to act in a moral fashion. In any case Apple satisfies the "open source morality" issue since they have also made recent contributions, for example their formerly closed source HFS+ code.

      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature. The optomists are losing badly.

      Untrue. We've seen various GPL based projects in financial trouble and begging for donations as well, including Linux distributions. Also, in general profit with open source is often said to be from consulting. Whether a project is GPL or BSD based has little effect, you could even argue that BSD has an advantage since it is easier to get into a corporation and a corporation may not want to share the changes they paid for.

    3. Re:Problem with BSD licencing by Plunky · · Score: 2, Funny
      The thing to me that most sucks was that Stallman and the BSD folks basically made a bet on human nature. The optomists are losing badly.

      You might consider me one of those optomists, since I release software under the BSD licence.

      How have I lost anything? I gave what I had away, with no expectation of rewards..

      In fact I gained something. I gained the smugness I am showing to you now.

  7. Re:Classic Theo de Raadt by Tweekster · · Score: 2, Informative

    from what i read was that he didnt like the binary drivers...fair enough that is his belief. some people did do a reverse engineer job and were asked to stop. it is germany on the other hand, not the US, they probably have a bit saner laws regarding that (depending on the method of course) maybe they did it out of respect and not fear. who knows. it could be a number of reasons. however, theo wasnt exactly an asshole on that concept, he is suprised they would stop (again we dont know why they stopped) he wished they didnt, he takes issue that they did stop. his opinion mismatched with someone elses. oh well it happens but its not like you said, he didnt slag linux. oh and he does do a lot of advocacy...wireless drivers for instance.... man I never thought I would defend theo

    --
    The phrase "more better" is acceptable English. suck it grammar Nazis
  8. Re:Iff..... by Theatetus · · Score: 3, Informative
    Can anyone tell me why BSD with it's enhanced security isn't incorporated into most Linux distros? How Unix like is it actually?

    Where to start?...

    BSD is an operating system. It consists of a kernel (like linux), a userland (like GNU), and a bunch of applications which are largely source-compatible with Linux.

    The BSDs share the fundamental gcc/gas/ld toolchain with GNU, but pretty much everything else (particularly the C library and make) they have their own version of. It is *possible* to run the BSD system on Linux (though not very easy), and actually very easy to run the entire GNU system on BSD. But they are different projects.

    OpenBSD was the result of a squabble between Theo and the NetBSD team. This was a felicitous squabble for the rest of us, because OpenBSD is a great operating system.

    --
    All's true that is mistrusted
  9. Re:Iff..... by Eightyford · · Score: 2, Informative
    Can anyone tell me why BSD with it's enhanced security isn't incorporated into most Linux distros?
    Because BSD is an Operating System, and GNU/Linux is an operating system... try reading that article again.
    And you should probably try to understand what the original poster actually meant. How about, "why doesn't linux implement parts of BSD into it". Understand now?
  10. Re:Iff..... by ArbitraryConstant · · Score: 3, Interesting

    "Can anyone tell me why BSD with it's enhanced security isn't incorporated into most Linux distros?"

    It's not a simple matter of importing code, to duplicate the changes in the Linux kernel and the GNU toolset would be prohibitively difficult. Also, much of the improved security comes at the expense of performance or functionality.

    --
    I rarely criticize things I don't care about.
  11. Job interview question by Anonymous Coward · · Score: 2, Insightful

    I was recently asked in a job interview "If Theo de Raadt and Dan Bernstein were locked in a room with knives, who would you want to come out alive?"

    (and my interviewer is probably reading this, in which case, "Hi there!")

    I said I wanted Dan Bernstein to come out alive, because I actually use his stuff in production as opposed to OpenBSD... but after thinking about it for a while I realised that OpenSSH is perhaps more important that Dan Bernstein's stuff. I mean, Dan never updates qmail and any of his tools... Theo may as well bump him off for all I care. ;P

    1. Re:Job interview question by IgnoramusMaximus · · Score: 3, Funny
      I was recently asked in a job interview "If Theo de Raadt and Dan Bernstein were locked in a room with knives, who would you want to come out alive?"

      At which question I would have gotten up, broken off a leg table, and proceeded to ask "Where are they?!" so that I can proceed to give Dan a hand, musing to myself that it is at times like these that I wish I were a gun nut.

      I am afraid this kind of a reaction would have been rather popular amongst those who had a pleasure of reading Theos' "conversations" with people on some of the USENET groups of old. Theo is just such a charming, loveable guy that swiss army knives open spontaneously in people's pockets at the very mention of him.

    2. Re:Job interview question by IgnoramusMaximus · · Score: 4, Insightful
      The exact reply to the question didn't really matter. The amount of time you think about it is what I look for.

      Was it me, you would have found out that it takes only 0.3 seconds to have a horrible accident with your coffee spilling all over your lap. Applogies and all that, why, I am just such a horrible klutz!

      Joking aside, but that sort of question would have me thanking you for the lovely opportunity to get interviewed by you, followed by a mental note not to ever do business with you, under any circumstances.

      Has it ever occured to you that these types of smart-ass, self-congratulatory questions, main purpose of which is to show who is the smart alpha-dog in that interview room, are absolutely useless in ascertaining someone's workplace abilities? Oh, what am I talking about, if it had, you would not be asking that and all the other ridiculous "logic" puzzles I am sure you are inflicting on your poor hapless, victims ... err ... applicants.

  12. It's not just openSSH by Theatetus · · Score: 5, Informative

    If you're a Linux user and you like your madwifi driver, you can thank the OBSD ath driver. Also if you ever want a RALink driver, OpenBSD is the only OS that has one right now and it seems almost certain any ports will be based off it. Anonymous CVS? Theo came up with it after NetBSD kicked him off the commit list. Randomized mmap, stack protection ... there's a lot of development being taken from openbsd. We've all got an interest here.

    --
    All's true that is mistrusted
  13. As a California Corp Apple helped pay for BSD by AHumbleOpinion · · Score: 2, Interesting

    Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products. What part of the BSD license does Theo not understand? Apple and SCO aren't "freeloaders", they are using the software under the intended license.

    No, it's far simpler than that. Apple and SCO *paid for* BSD. BSD was paid for by the taxpayers of California, including corporations like Apple and SCO. Perhaps Theo noticed a "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved" somewhere in his review of the source code. Perhaps Apple and SCO believe they have contributed more than Theo. Besides cash Apple has also contributed formerly closed source, for example the HFS+ support in Darwin. Self serving, so what, Theo, RMS, and a host of others aren't?

    I use OpenBSD and despite Theo's nonsense I support it by buying a CD every year. If Theo want's his pet projects funded he needs to learn to stop pissing off large potential contibutors, DARPA for example.

  14. Re:I bought the T-shirt by bhima · · Score: 2, Interesting

    I hope so! I did to and I did it because OpenBSD is rapidly becoming the only OS I trust enough to mount a rented DVD on and be absolutly sure I don't wind up with any sneaky malware...

    --
    Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
  15. Sounds almost like a threat by Baki · · Score: 2, Interesting

    Especially "or maybe that has happened already". Is the great diplomat Theo de Raadt now resorting to extortion?

    1. Re:Sounds almost like a threat by Valar · · Score: 4, Insightful

      No. It would be extortion if he were threatening to put security holes in SunSSH. He's just saying that without Sun's support, he can't be expected to analyze and warn them of bugs in their product. Or are you saying I have a legal requirement to disclose every bug I notice in every piece of software I use to the developer?

  16. Folks are completly missing the point... by John+Whorfin · · Score: 4, Informative

    It's not that the Foo Corp is using OpenSSH w/o paying Theo or the OpenBSD/OpenSSH crowd. No one (including Theo) has a problem with that.

    It's that some companies *cough*Sun*cough* make all kinds of noises about being "open" and "supporting open source" and market the crap out of it purely because it's the latest buzzword, when in reality they just don't give a shit.

    That's what gets to Theo... and others.

    1. Re:Folks are completly missing the point... by cant_get_a_good_nick · · Score: 2, Interesting

      I won't comment on the money issue, i think a lot of people should be contributing for OpenSSH. The problem is that the BSD license doesn't require it. You can say that it should have, but i bet OpenSSH wouldn't be as ubiquitous as it is now. We have a bunch of hardware devices that we connect to with ssh. The fact out of all those devices, Theo only got a grand really surprises me.

      But as far as buzzword jumping - Sun has given a lot of things to open source, more than IBM in fact. NFS was developed by Sun, was always free as far as i know. Bill Joy, one of the Sun founders, was heavy into adding things to BSD (the original, from UC Berkeley) which were released for free. They jsut released their entire OS. They gave away ZFS and dtrace recently. They aren't on it because it's the latest buzzword. They've been doing it for years.

  17. Anti-Theo sentiments are muddying the point here by twigles · · Score: 5, Interesting

    Theo may be a jerk, but that's not the point here. The OpenBSD team does great work that gets ported to other platforms or just flat out embedded, but no one wants to lend a hand. This interview did not strike me as whiney or greedy; Theo never came across as wanting to get rich, with his grand aspirations of paying travel expenses for poor developers.

    His request is very reasonable - everyone is benefitting, and those who are in a position to give a little back should do so. He didn't say fund the project, he said contribute a little. Jeez, anything really.

    This whole Slashdot anti-Theo movement is lame, it's like watching jocks push the nerdy quiet kid around in high school, which is a bit ironic considering that many of us *were* those nerdy quiet kids. Stop trying to be part of the "in" crowd by bashing this guy and read the article with an objective eye.

  18. ... and licenses by John+Whorfin · · Score: 4, Informative

    A while back -- pre-SCO -- OpenBSD did a "license audit". I don't have the list in front of me but a sizable number of reasonably well-known open source projects had questionable licences. Theo really did ask nicely and got most of them changed.

    TCP Wrappers IIRC was one of them, pppd another (again IIRC).

    Like Theo or hate him, he's done more for the Open Source community than just piss people off.

    1. Re:... and licenses by justins · · Score: 2, Informative
      A while back -- pre-SCO -- OpenBSD did a "license audit". I don't have the list in front of me but a sizable number of reasonably well-known open source projects had questionable licences. Theo really did ask nicely and got most of them changed.

      TCP Wrappers IIRC was one of them, pppd another (again IIRC)

      I'm pretty sure Wietse Venema saw the value in updating the licenses for TCP wrappers and (perhaps more importantly) Postfix when approached by Theo and did so without any drama whatsoever. Of course, when there's no drama it doesn't make front page geek news...
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  19. Pony up by Graabein · · Score: 4, Insightful

    An OpenBSD CD set is $49. If you've ever used OpenSSH or x.org X11 (read the article), you've already got your money's worth. In addition, chances are that somewhere in your organization (or at your house?!?) there's an OpenBSD-based firewall happily chugging away with PF and CARP.

    So cut the anti-BSD crap and get over Theo's personality for like 10 seconds and pony up. Some day you'll be glad you did. If for no other reason, do it in your own best interest.

    --
    And remember kids: Never trust a computer you can actually lift.
    1. Re:Pony up by awing0 · · Score: 2, Interesting

      I know OpenSSH has saved me more than $49 on gas alone. Even though I don't use OpenBSD as often as Linux or FreeBSD, it's well worth it to fund such a polished software project. I'm ordering 3.9 right now.

      --
      Cthulhu Saves.
  20. It's not about code but MONEY by paugq · · Score: 5, Insightful

    What's so difficult to understand for those GPL zealots out there?

    Theo is NOT talking about code. He couldn't care less about the code!

    He's talking about MONEY. OpenBSD and OpenSSH need money to pay Theo's (and other's) income, bandwidth, servers, etc. How does the GPL help when you need money? It does NOT help!

  21. BSD vs GPL is not relevant by AHumbleOpinion · · Score: 3, Informative

    I say onto Theo: Tough Cookies! You made your bed, you sleep in it!

    BSD vs GPL is not relevant. Theo's bed was made by driving away potential sources of income like DARPA.

    1. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 4, Insightful
      BSD vs GPL is not relevant. Theo's bed was made by driving away potential sources of income like DARPA.

      Yes it is, as a part of a very long list of good advice he received over the years on a lot of things, and all of which he proceeded to sneer and snicker on, as only Theo can. DARPA's help is just one item on that very, very long list.

    2. Re:BSD vs GPL is not relevant by AHumbleOpinion · · Score: 3, Informative

      "BSD vs GPL is not relevant. Theo's bed was made by driving away potential sources of income like DARPA."

      Yes it is, as a part of a very long list of good advice he received over the years on a lot of things


      No, that's a fallacy. In general under open source the money is in consulting, not in the development. A BSD based project is more likely to get inside a corporation and possibly more likely to create consulting work. Whether a project is BSD or GPL, if someone doesn't want to code themselves, they can hire others to do the work. The only difference is whether that work goes back to the community at large and for the company that needed specialized changes that is irrlevant and it may even be counterproductive to the company. The GPL is not some magic pill. We've seen numerous GPL based projects in financial trouble and begging for donations around here as well.

    3. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 3, Insightful
      No, that's a fallacy.

      Oh, really? You mean it does not depend on what the purpose of the project is?

      In general under open source the money is in consulting, not in the development.

      Oh I see, making money for Theo was the whole idea of OpenBSD? NOW you tell us!

      A BSD based project is more likely to get inside a corporation and possibly more likely to create consulting work.

      Which is a good thing if you are planning to make people appropriate, modify and sell your code while not letting you look at it ever again, in hopes that somehow your celebrity status will make some of them hire you.

      Whether a project is BSD or GPL, if someone doesn't want to code themselves, they can hire others to do the work.

      True enough, that is why BSD offers no advantage over GPL in this area.

      The only difference is whether that work goes back to the community at large and for the company that needed specialized changes that is irrlevant and it may even be counterproductive to the company.

      Which, in most cases, as Theo is finding the hard way, is the only type of return expected from commercial involvment in your project. Hoping to get hired by someone using your code is wishful thinking in vast majority of cases. GPL folks understand that, and operate accordingly.

      The GPL is not some magic pill. We've seen numerous GPL based projects in financial trouble and begging for donations around here as well.

      Of course it is not. But it was never its purpose. The purpose of GPL is to ensure that regardless of who is using or contributing to the code, and regardless of financial circumstaneces of a project, the code remains the property of the community and cannot be stolen and then sold back to us. That is all.

    4. Re:BSD vs GPL is not relevant by AHumbleOpinion · · Score: 2, Interesting

      Oh I see, making money for Theo was the whole idea of OpenBSD? NOW you tell us!

      Unless they are academics and thereby have their open source development efforts subsidized they have to generate some sort of income to keep their pet projects going and avoid having to get "real" jobs.

      "A BSD based project is more likely to get inside a corporation and possibly more likely to create consulting work."

      Which is a good thing if you are planning to make people appropriate, modify and sell your code while not letting you look at it ever again, in hopes that somehow your celebrity status will make some of them hire you.


      Not celebrity status, expertise with the code. It takes time for a 3rd party to learn and become proficient with someone else's code. The most cost effective way of getting the changes you want may easily be to hire the original author.

      Which, in most cases, as Theo is finding the hard way, is the only type of return expected from commercial involvment in your project. Hoping to get hired by someone using your code is wishful thinking in vast majority of cases. GPL folks understand that, and operate accordingly.

      In part that is another fallacy. Most work on GPL'd code is never seen by the original authors or the community. Most software is internal, it is not distributed outside the company, and the GPL does *not* require the changes to be returned to the community unless thers is public distribution. Technically you only have to share the changes with those you distribute executables to, so two companies could share work and keep the community in the dark. FWIW, the majority of software being for internal consumption is the real lock Microsoft has on the market.

    5. Re:BSD vs GPL is not relevant by IgnoramusMaximus · · Score: 2, Interesting
      Unless they are academics and thereby have their open source development efforts subsidized they have to generate some sort of income to keep their pet projects going and avoid having to get "real" jobs.

      Vast majority of FOSS projects are either after-work hobby efforts or side-effects of some other paid work. It is a testimony to Theos' ego, for him to assume that he will be funded just because his project is sooooo much more important then all the others.

      Not celebrity status, expertise with the code.

      Proficency with code can be acquired, and most of the time other factors play the primary role, such as geographical locations, existing teams, well proven employees and managers, corporate politics and what not. Again, as Theo is finding the hard way.

      It takes time for a 3rd party to learn and become proficient with someone else's code. The most cost effective way of getting the changes you want may easily be to hire the original author.

      You could hire whole armies of programmers, have them dine at 5-star restaurants, be enterntained by live performances by the most expensive actors, while on one of their 20 scheduled breaks during the day, and still not arrive anywhere near the financial and psychological cost of having Theo "work" for you. People have jumped off tall buildings to escape far less aggravating situations, such as hammer-totting mafia debt collectors.

      Seriously, you have a horrible propensity to massively oversimplify things. Vast majority of FOSS programmers never gets approached by commercial interests, even though they are using the projects extensively, as most companies would rather use an existing in-house development team or local, proven consultants. That is how businesses work.

      It case of the project contributors seeking to be hired, their options are the same as those of any other software maker: self-promotion and salesmanship. Which requires inter-personal skills. Which Theo is utterly devoid of.

      In part that is another fallacy.

      You are fond of saying "fallacy", in an effort to pre-emptively discredit your opponent, and yet lack any ability to demonstrate any such "fallacies". Not a very respectable debating tactic.

      Most work on GPL'd code is never seen by the original authors or the community. Most software is internal, it is not distributed outside the company, and the GPL does *not* require the changes to be returned to the community unless thers is public distribution.

      In which GPL is indistinguishable from all the other licenses. And which internal work is again performed by internal, pre-existing teams, with an occasional posting on a project's mailing list being the only indication of any desire for external input. None of which of course alters my points in any way, as the resulting code cannot be sold to anyone, or distributed in any way externally, without running afoul of the GPL.

      Technically you only have to share the changes with those you distribute executables to, so two companies could share work and keep the community in the dark.

      Err, no. As soon as you begin any external "distibution", any old clown who gets the whiff of this can show up and demand both binaries and source. Such is the way of the GPL.

      FWIW, the majority of software being for internal consumption is the real lock Microsoft has on the market.

      Microsofts position has a myriad of reasons, and is another, wholly off-topic, conversation.

    6. Re:BSD vs GPL is not relevant by PietjeJantje · · Score: 2, Interesting

      Me, I don't see a particular difference between the two licences for programmers.
      It will be you and your buddies coding, anyway.
      If you want to earn money, buy a lottery ticket. You can earn money with open source, if you're the one in 1 million coders who's lucky.
      Me, I don't mind if EvilCorp takes my stuff and tries to sell it with their added value to monkeys on Mars, as far as I'm concerned. I don't see how this effects my life, or makes my code less free. BSD is for strong people who believe in themselves.
      What gives the MIT/X/BSD licenses the edge for me is that there are no hippies or fanatics around (see: above) telling me what to think and do or otherwise trying to sell me their truth. Really. I find it particularly disturbing that according to Stallman, if I'm a hairdresser or a butcher I can sell my services, if I'm a programmer I must be a hippie for the good of mankind and sell T-shirts. This view is outdated, and was out of this world to start with. Although I agree I can think up an argument why humanity needs a free operating system, for 99,9% of the open source projects, humanity will fair just fine without it. Besides that, try to sell this hippie story to a victim of war, poverty or aids in Africa, just to alter that perspective. Last but not least, humanity got out of the situation where they sit around fires and slept in caves, by specializing and inventing money as a means of exchange. For Stallman, programmers need to step out of that. That's fine, but the rest of the world doesn't. My hairdresser doesn't have the same attitude, he wants my money.

    7. Re:BSD vs GPL is not relevant by turbidostato · · Score: 2, Insightful

      "according to Stallman, if I'm a hairdresser or a butcher I can sell my services, if I'm a programmer I must be a hippie for the good of mankind and sell T-shirts."

      Outstanding bullshit. It is *exactly* the opposite!!!

      According to Stallman, if I'm a hairdresser or a butcher, I can sell my services, if I'm a programmer I can sell my services too!

      The question is that since the hairdresser won't ask you for money each time somebody see your hair, or a butcher will ask you for money when you buy the meat, but he won't ask for more money if you use it to invite your friends (multiuser license), or if you resell it, the programmer should ask for money against their services (coding) but shouldn't add any kind of extortion about further usage of what you coded, just the same the hairdresser or the butcher won't ask for more than the fair value of their services (cutting hair or selling meat).

  22. Well, by Joseph_Daniel_Zukige · · Score: 5, Insightful

    I have thought along similar lines, but it really demonstrates something that we must quit ignoring.

    "Free" is an illusion.

    When we use "free" software, we pay for it one way or another. Time or money, and, no, time is not money.

    Money is green stuff that you through around on the crops to make things grow, as somebody in some famous musical once said, quoting somebody else, I'm sure. When you collect too much money in one place, it goes fetid.

    Time is the true currency, although too much time can go fetid as well.

    The licenses are gentlemen's agreements. It's a trade of time for time, with rules of courtesy. (EULAs are _not_ gentlemen's agreements, I am not taking about those licenses, they don't deserve to be called licenses.) The licenses form the ground rules for the community that forms around the software. It's very much like the old guilds, although much more open in a very good way.

    With the GPL, some of the rules of courtesy which are important for maintaining the infrastructure of the guild are explicit. We might assume that this is because Stallman is a cynic, or because he is a realist, but must people are still confused and think he is an idealist.

    With the BSD license, the rules are implicit, derived from the external society, the (Christian, though not entirely uniquely so in the current view of history) principle of casting one's bread on the water. It is expected that the waters will bring the bread back, multiplied. And this is where things have broken down.

    Even under the BSD license, the rules of giving back are natural laws, and are not suspended. Humans whose primary product are sales presentations have no idea that they have to give back or the resource will be depleted. Stallman recognized that, Theo has not yet.

    People have to be reminded to be courteous, and that's why an idealist and general nice guy like Theo ends up making enemies. The license doesn't remind people, so he has to spend his energy reminding them.

    Putting new source under GPL would be one solution, but, as is well known, it is not one that can really be considered yet. A new modified BSD that contains a non-binding reminder that the resources don't renew themselves may be what's in order right now.

    1. Re:Well, by Plunky · · Score: 3, Insightful
      With the BSD license, the rules are implicit, derived from the external society, the (Christian, though not entirely uniquely so in the current view of history) principle of casting one's bread on the water. It is expected that the waters will bring the bread back, multiplied. And this is where things have broken down.

      You imply that things have broken down because the bread never came back, but I would point out that the broken part was expecting it to.

      I write software and release it under the BSD licence because I dont care to lock it up. I dont care if somebody makes millions out of it, I wrote it because I wanted to, and released it because I wanted to.

      My opinion is that if the BSD licenced OS project that I am using goes belly up, it doesnt really matter. The code is still there and the people who write it are still here (if not the original ones, new programmers are born every minute) and the principle is still here. BSD4.4 is dead, but XxxBSD is not. If XxxBSD dies, YyyBSD will come along shortly.

      Now, I can see Theo's point about companies not giving anything back, but that is simply their bad karma and one day it may bite them.

  23. Let's Add Some Context Here by Noksagt · · Score: 5, Insightful
    First, I think the OpenSSH question was baited. Even disregarding that, you excluded an insightful caveat from Theo's reply:
    Of course we did not set out to create OpenSSH for the money -- we purposely made it completely free so that the "telnet infrastructure" of the 1980s would die. But it sure is sad that none of these companies return even a fraction of value in kind.
    He acknowledges that not only was there no obligation for these companies to donate money, but that OpenSSH wasn't created to make money. I don't think it is unreasonable for him to ask for money, particularly when he has pointed out that some of the vendors selected OpenSSH after they were quoted high fees (multi-millions of USD) from the commercial SSH vendor.

    OpenBSD has done good work & currently depends on receiving financial donations. Enlightened companies should notice that OpenBSD needs some funding right now & that it would be cheaper to fund them than to have to adopt the support and development of the OpenBSD products they use.
  24. Be fair by grahamsz · · Score: 3, Informative

    Sun bought and open sourced both StarOffice and Netbeans, they've open sourced Solaris and the UltraSPARC processor core.

    I'm sure there are plenty other projects, but Sun have donated what must amount to many millions of dollars of code to the community.

    Sure they use other open source projects (in line with their licenses) and while they presumably aren't throwing money at Theo it seems unfair to brand them as anti-opensource when they've done a lot of good.

  25. Check your dates by Noksagt · · Score: 2, Informative
    "Some of the OpenSSH freeloaders, like Apple Computer..." Apple and SCO aren't "freeloaders", they are using the software under the intended license.

    No, it's far simpler than that. Apple and SCO *paid for* BSD. BSD was paid for by the taxpayers of California, including corporations like Apple and SCO. Perhaps Theo noticed a "Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California.
    OpenSSH development began in 1999. So, no Apple didn't pay for OpenSSH. Yes, tax payers paid for the original BSD, from which NetBSD borrows from (and OpenBSD forked from NetBSD). (Though I think it was probably mostly funded under a federal grant, rather than state taxes.)

    In any case: development and maintenance costs don't magically stop when there is no tax-funding of the project. If people want it to survive, they do need to continue sponsoring it.
  26. Re:I love OpenBSD by Noksagt · · Score: 4, Insightful
    Does Google pay for Linux and Apache?
    Google does submit patches to these projects and has sponsored interns and employees work on various open source projects.
    Does Yahoo pay for FreeBSD
    Yahoo! hosts the freebsd.org cluster. They pay bandwidth and power and most of the hardware. They even give hardware to developers and employ several coders for the project fulltime.
    does Apple?
    I don't know Apple's financial commitment. They do give code back. Furthermore, they have really forked FreeBSD, so aren't directly using all of the "upstream" support, maintenance, development, etc. of FreeBSD.
  27. Oh really? by Deorus · · Score: 3, Informative

    > Also if you ever want a RALink driver, OpenBSD is the only OS that has one right now and it seems almost certain any ports will be based off it.

    I thought RALink supported Linux themselves, otherwise, what's this?

    1. Re:Oh really? by malloc · · Score: 3, Insightful

      *that* is called a binary blob driver. It means if you're willing to give control of what kernel you run to this company then you can use their driver. Essentially this boils down to them controlling your whole machine and is why Linus refuses binary drivers. ("No, you can't use this new kernel feature", "no, you can't debug this crash", "sorry, we're out of business, you can't upgrade your kernel ever again") There's nothing to praise about that.

      Malloc

      --
      ___________________ I want to be free()!
  28. Re:More importantly: by mcc · · Score: 2, Informative
    That is interesting. I did not know that.

    However, I do notice that when I actually test on my Mac OS X machine here:
    $ cd /usr
    $ grep -ri "freebsd" . | wc -l
            2889
    $ grep -ri "openbsd" . | wc -l
              663
    And it seems that besides there being more of them, the freebsd matches are more "real"-- if i look at the actual matches the FreeBSD ones consist to a great extent of matches in actual basic binaries and libraries, whereas the OpenBSD matches that aren't actually matching OpenSSH binaries seem to mostly be compatibility code in crossplatform UNIX apps-- "#ifdef openbsd" blocks in X11 headers for example (right before the #ifdef amiga ones), which clearly are not an indicator of OpenBSD crosspollination in OS X.

    And then trying again, in the source for Apple's libc:
    $ cd Libc-391.2.5
    $ grep -ri "freebsd" . | wc -l
            1179
    $ grep -ri "openbsd" . | wc -l
              63
    And even here again most of the occurances of OpenBSD maybe shouldn't count to the total, since they are, well, in some big directories named "FreeBSD/". It looks like a lot of those 63 matches were patches that were ported upstream to FreeBSD, then sucked into Darwin from there.

    So these were just the first two things I thought to check, and in both cases FreeBSD strings show up more often than OpenBSD by a very significant majority. I can totally believe that Apple is making much more direct use of OpenBSD code than I was aware of, but if you do not mind me asking, exactly *where* in OS X am I supposed to be finding this effect you claim of "grep... you will find more occurrences of OpenBSD than NetBSD and FreeBSD"? Because so far I'm not seeing it at all.
  29. Re:Iff..... by IcePic · · Score: 2, Insightful

    like why glibc wont have strl*()-functions which may improve security:
    http://lists.debian.org/debian-devel/2002/03/msg00 309.html

    It's not like the whole linux world would fall apart if there was some more
    string functions which would not go ape on weird inputs.
    I know strl*() isn't a magic bullet to prevent all kinds of badness, but they
    really can't be worse than the same functions without bounds checking.

    Still, better to bash some BSD...

    --
    -- I'm as unique as everyone else.
  30. Fork it! by scarolan · · Score: 2, Insightful

    Our company would be more inclined to donate if we knew that the money we gave would go directly to support OpenSSH. We have no interest in supporting OpenBSD. Fork OpenSSH into it's own project with separate financing and management, and we'll send you some money.

    1. Re:Fork it! by merdaccia · · Score: 4, Insightful

      Then people wonder why de Raadt behaves the way he does. When I read this post, my first reaction was to send you to hell with enough bad language to put you in a first class seat. Maybe that's why de Raadt gets his stigma, by not taking a pause from his first reaction.

      So you want to know that the money you give would go directly to support OpenSSH? According to de Raadt, there are six developers that focus on OpenSSH. These developers also work on other aspects of OpenBSD. What exactly do you want them to do? Divide your money between the six of them according to how many hours each works on OpenSSH? Do you want them to have separate network connections and hardware, and pay for it with your donation? How do you compensate the other OpenBSD developers when their ideas and contributions inevitably end up in the OpenSSH codebase?

      The OpenBSD developers are a group of people working together. OpenSSH is the fruit of their work. The way to contribute directly to OpenSSH is to contribute funds to its developers. That's exactly what contributing to OpenBSD does, because the developers of OpenBSD and the developers of OpenSSH are one and the same.

      So contrary to your second sentence, you have every interest in supporting OpenBSD. Saying otherwise is a disingenuous and pathetic attempt at justifying your reluctance to reward the people whose work you claim to respect.

      --

      *blinking cursor*

    2. Re:Fork it! by Myrrh · · Score: 2, Informative

      Theo mentions in the interview how it would not be advantageous to become a non-profit organization. I'm not sure where he and his developers operate, so I can't speak to the specific laws of his country.

      But, incorporating (for-profit or otherwise) is not difficult and needn't be expensive, either. Were he to do so, he could adopt articles of incorporation and bylaws which would clearly state the divisions of the company. He could create an "OpenBSD" division and, similarly, an "OpenSSH" division.

      Maintaining some documentation that would be open to review by interested parties would likely go a long way toward placating companies who would like to contribute financially, but are loath to do so because they have no assurance their funds won't be going directly to OpenBSD development. There should be a way for interested parties to earmark their funds for one or both projects, and have some assurance that their funds will be used properly.

      Theo refuses time and again to accomodate such requests, and therefore he is forever grousing about how so many companies refuse to provide financial support in exchange for OpenSSH, which supposedly significantly enhances these companies' bottom line.

      I really believe that if he were to take a bit of time off from coding to contact a CPA or attorney (heck, he could probably get it pro bono if he turned off the vitriol for a little while), formulated a sound business plan and filed articles of incorporation, and then presented his case to these companies he is so fond of complaining about, he just might see some funds come his way.

      I think, though, that he would rather complain than actually get something done about it.

  31. Absolutely by theolein · · Score: 4, Funny

    This whole Slashdot anti-Theo movement is lame

    I agree wholeheartedly.

    -Theo

  32. Re:I love OpenBSD by justins · · Score: 2, Insightful
    Someone would probably give OpenBSD a grant, but Theo has already proven he doesn't know when to shut up and has problems playing with others.

    A careful reader of the interviews that come up with Theo occasionally will note that he's pretty good about endorsing the companies who actually support the project. Just in that short interview he mentioned a couple of wifi chipmakers who actually share information. The expectation is that the open-source concerned reader will support those companies in favor of the ones which are mentioned who do not share information.

    Past experience suggests that the average Linux kiddie is more likely to take the binary driver and run, particularly if there's game playing to be done. But it seems Theo's doing a reasonable job of supporting the supportive vendors.
    --
    Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  33. Jerry A. Taylor, call Theo today! by NXIL · · Score: 3, Insightful

    Jerry A. Taylor
    City Manager
    Tuttle, OK

    Dear Jerry,

    you like secure operating systems. So does Theo de Raadt: he loves them!

    Please contact Theo directly at *deraadt@cvs.openbsd.org*

    Be firm: Theo will help you, but only if you are make it clear that you expect help, and you want it now. (I think that when you contacted CentOS's team, you were sort of beating around the bush. That won't work with the OpenBSD team. Be direct!)

    Theo will respect your 22 years of IT experience. And, I think he will be impressed that you worked at Raytheon--wow!

    No need to call the FBI to get a response from Theo and his boyz. Enjoy!

    --A concerned citizen

  34. Re:Is it bad business sense if it's done anyhow? by Trelane · · Score: 2, Insightful
    If the company pays the OpenBSD team, the code gets written, but if it does not pay, the code still gets written.
    Excellent point, although not quite completely true:
    As long as the OpenBSD team is writing code without requiring payment, it makes far more sense for the company to not pay.
    By short-term metrics, this is certainly true. However, your above statement isn't 100% correct. So long as someone (or a group of someones) is supporting the development, the code will get written. As (I believe) you've said before, programmers gotta eat. So they will first seek subsistance (their job), and once that's been satisfied, they'll be coding for their own use and for the greater good. Maslow's hierarchy of needs and all that.

    So while it makes sense on the short-term microeconomic level to not pay anything to a project you use, it makes no sense on the long-term macroeconomic level--just as a single family saving money is a wise investment, all families saving money is a recession.

    The optimal solution here is for users to pay some money to projects they wish to use. This is a modest, compromise amount, causing the greatest good in the short- and long-terms, and in the micro- and macroeconomics.

    Sadly, it seems that the corporate world (and most of the average user world too) is only too happy to sacrifice long-term gain for short-term gain. So conventional modern business practices would likely be in agreement with your statement.

    --

    --
    Given enough personal experience, all stereotypes are shallow.
  35. It's hard for a company to support OpenBSD by Ritchie70 · · Score: 2, Interesting
    In a company of any size, there are a million checks and balances before money gets sent out.

    To donate to OpenBSD you write a check to Theo. There's no OpenBSD foundation, no non-profit, nothing. So I'm supposed to go to my boss, who has to explain it to his, who has to explain it to his, to get a check cut to some guy in Canada because he does good stuff? I might be able to get a CD on the corporate AmEx, but a donation of any real size? No way!

    If Theo wants money, Theo needs to set up a non-profit, preferably US-based, get tax exempt status, and see what happens. It isn't nearly as hard, complicated, or expensive as he thinks.

    --
    The preferred solution is to not have a problem.
  36. Let's be Objective about this, was Re:Hmm... by bourne · · Score: 3, Insightful
    Bravo; you've made the most secure operating system available today. But, then, you have this firmly held belief that the rest of the world owes you something? That you're gracing the rest of the world with your glorious presence and regal software? That attitude is not welcome here.

    Actually, no, he's not claiming that the world owes him something. He's claiming that his act of creation and contribution does not cause him (well, specifically, the OpenSSH developers) to be owe anything further to the people who take advantage of their contribution.

    That is an entirely different issue.

    "From the beginning of history, the two antagonists have stood face to face: the creator and the second-hander. When the first creator invented the wheel, the first second-hander responded. He invented altruism.

    "The creator - denied, opposed, persecuted, exploited - went on, moved forward and carried all humanity along on his energy. The second-hander contributed nothing to the process except the impediments. The contest has another name: the individual against the collective." - Howard Roark in The Fountainhead by Ayn Rand.

    1. Re:Let's be Objective about this, was Re:Hmm... by coolGuyZak · · Score: 2, Funny
      From the beginning of history, the two antagonists have stood face to face: the creator and the second-hander. When the first creator invented the wheel, the first second-hander responded. He invented altruism.
      At least the first second-hander was still being original--before that, theft didn't exist. What we really should be careful of are those second second-handers.
  37. Grow up! by phliar · · Score: 2, Insightful
    Jesus Christ, all this TdR flaming is getting ridiculous. His philosophy is clear: he cares about the code, and only about the code; he's not interested in marketing or market share or advocacy. He's a smart guy who doesn't suffer fools gladly, and the Internet makes it possible for every fool to contact him. Small wonder the fools think he's an asshole. (The pity of it is: he really is a pretty nice guy who even has interests other than OpenBSD.)

    Since it's obvious that many here haven't actually read what they're flaming about, here's the last question of that interview:

    NF: Lots of hardware vendors use OpenSSH. Have you got anything back from them?

    TdR: If I add up everything we have ever gotten in exchange for our efforts with OpenSSH, it might amount to $1,000. This all came from individuals. For our work on OpenSSH, companies using OpenSSH have never given us a cent. What about companies that incorporate OpenSSH directly into their products, saving themselves millions of dollars? Companies such as Cisco, Sun, SGI, HP, IBM, Siemens, a raft of medium-sized firewall companies -- we have not received a cent. Or from Linux vendors? Not a cent.

    Of course we did not set out to create OpenSSH for the money -- we purposely made it completely free so that the "telnet infrastructure" of the 1980s would die. But it sure is sad that none of these companies return even a fraction of value in kind.

    If you want to judge any entity particularly harshly, judge Sun. Yearly they hold interoperability events, for NFS and other protocols, and they include SSH implementation tests as well. Twice we asked them to cover the travel and accommodation costs for a developer to come to their event, and they refused. Considering that their SunSSH is directly based on our code, that is just flat out insulting. Shame on you Sun, shame, shame, shame.

    I will say it here -- if an OpenSSH hole is found that applies to SunSSH, Sun will not be informed. Or maybe that has happened already.

    Sounds completely reasonable -- just calling a spade a spade and not trying to sugar coat anything.
    --
    Unlimited growth == Cancer.
  38. Re:Classic Theo de Raadt by LurkerXXX · · Score: 2, Insightful
    He said he found it crazy that folks who always want 'open' software, even forcing anyone using it to keep it open, would accept closed binary blobs in their software. That sounds like a pretty specific point he was talking about. Not 'slagging linux developers in general'.

    If you disagree with his point, how about stating why you think it's wrong rather than just bitching about 'classic theo'.