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.

21 of 476 comments (clear)

  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. 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.

  3. 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?

  4. 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.
  5. 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!

  6. 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.

  7. 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.

  8. 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.
  9. 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.

  10. 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.

  11. 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.
  12. 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.

  13. 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.
  14. 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.

  15. 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.

  16. 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*

  17. 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.

  18. 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

  19. 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.

  20. 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()!