Shave the whales.
(or whatever a cup of coffee costs these days)
While on the subject it's worth mentioning the article from Ask Slashdot which nicely and detailed answers most of the questions you may have.
Actually, this is one of the best content articles I can remember on Slashdot... The graph in the middle is simultaneously funny and sad.
His name was one of the first I learned to recognize as a young beginner sci-fi-aficionado (ohh, maybe 10 years old?). I really liked the Steel Rat books, both others as well.
Here is a comment by John Scalzi (who is actually surprisingly similiar in style - I recommend).
No, this isn't 'Interresting', rather mod as 'Blathering'.
Well, there is no point denying that Theo isn't the most malleable person. But, as has been said here on
Theo, ranting, is why he got kicked off the NetBSD project.
While this is true, the history also proved him correct on many things (Charles Hannum was on the core team that did the kicking).
Theo, ranting, is why OpenBSD's drivers for Broadcom chipsets stink. (Look up how the original author tried to resolve the licensing problems of sticking his GPL drivers in an OpenBSD kernel and was ignored, then screamed at by Theo for making the issue public.)
That whole mess sucked. The OpenBSD developer that made the port (which was supposed to be a re-implemenation) f*cked up big time and imported GPL-files into the tree. The only thing positive in the whole affair is perhaps Theo's unconditional backing of his developer.
Theo, ranting, is why OpenBSD doesn't properly handle booting from software RAID.
It does (I believe the kernel must be on a non-RAID slice/disk, but that's no different to most other implementations).
Theo, ranting, is why the OpenBSD installer works like the UNIX crap I learned to loath back in 1985 and can't store the state of what you've already selected or go back, you just have to start over from scratch.
Actually, the very minimalistic installer is often hailed as one of the best and fastest in the industry. I don't think that there are that many installers where you can do the install by repeatedly pressing enter (and writing the hostname once) in that short time. And well, it's doesn't remember the state, but then again, you can restart it (a shell script) and start over without rebooting - that can't be said about many others.
Theo, ranting, is why OpenSSH has no built-in support for chroot cages.
This seems to disprove that. Unless you have different definition of 'chroot cage'.
Theo, ranting, is why OpenBSD has no virtualization server capability.
In many aspects virtualization contradicts the goal of security. Also, most VM solutions are proprietary, thus does not run on OpenBSD.
Theo, ranting, is why OpenSSH still stores both host keys and by default, user private keys in clear text with no expiration, and has no plans to fix this.
Yes, in clear text. Do you propose they should be encrypted? And where should the crypto key be placed? Perhaps... on disk? Hashed? If you are paranoid - use whole disk encryption. Because physical security is the key issue here as I see it. The keyfile is supposed to be user-readable only...
What is a reasonable default expiration time? No, there is no plan because the feature doesn't improve anything.
Theo, ranting, is why the "compatiblity chart" is a list of chipsets that don't match the actual chipsets published by the manufacturer, and usually are from chipsets at least 4 years old.
Uhmm, what are you talking about? You aren't... trolling?! Are you?
Theo, ranting, usually means you're doing something right for your actual client base rather than for his ivory tower.
No, here's where you actually are correct. Theo doesn't do shit for the users - he is only concerned with the goal stated above (free, fast, secure). The availability of OpenBSD to the userbase is actually a side-effect.
There's a reason OpenBSD is used only by fanboys who run it on "hobby" systems and don't get any work done.
Hehe, if anyone who uses an OS because he or she likes it is a fan then I guess we are all fanboys (and fangirls).
The vast number (but by no means being even close to a majority) of systems deployed on OpenBSD seems to contradict the second point.
And yes, I've dealt with the crap for years: I *wrote* the first SunOS ports of SSH-1, SSH-2, and OpenSSH.
Nico Kadel-Garcia, is that you?!
(Theo's fan club did not write SSH:
No one has said that. Neither does the manual.
they ported Tatu's previously GPL work into OpenSSH, and screwed up the license.
Excuse me? Tatu's first version was under a BSD-like license, later versions was changed to something incompatible which induced the fork.
And Sun/Oracle, Apple and IBM among others seems to like the license very well, considering they has imported OpenSSH into their own products.
Surprisingly little of the actual codebase is due to OpenBSD hosted development.)
15 years of development and countless of features seems to contradict that as well.
BTW, speaking of rants...