You might not run OpenBSD, but if you're running ssh on your Linux system, then you're actually running OpenSSH from the OpenBSD project. If you appreciate being able to access your systems more securely through ssh, please consider supporting the project by buying a CD set, tshirt or poster from them.
I'm not sure what you mean. Portable openssh is openssh + support for non-openbsd systems. This also includes things like pam support. I'd say that the "portable" part is almost all there is to the "portable openssh" project.
Its actually one of the easiest O.S to install and work with when it comes to back-end servers for running network infrastructure type services (vpn, firewall, chat server, torrent server, dns, dhcp etc. etc.) - nothing comes close.
What are some reasons for OpenBSD not being a more popular OS on web servers? I always wondered about this, as on paper OpenBSD (and FreeBSD) seem like they have the edge but most server admins end up running linux. Another case of linux being slightly easier to use and doing the job well enough?
I'm a big fan of FreeBSD/OpenBSD as server OS's. I've put OpenBSD/pf to great use as firewall machines, as they're VERY easy to configure, and the docs are most everything you need. FreeBSD has been great for general-purpose workloads.
For some time OpenBSD has been regarded as "slow", in big part because it couldn't use large amounts of RAM, and it scaled across multiple cores poorly. I'm not sure if this is still the case.
OpenBSD has never had performance as a driving criteria, and has for long time, both justly and unjustly, been considered "slow", especially on machines with more than two CPUs, when compared to Linux and FreeBSD. Though it's been 6 years or so since I did any sort of serious large scale sysadmin work with it so I don't know if things have changed.
OpenBSD is not friendly to the kind of newbie who prefers HOWTOs, GUI admin tools, etc. It does have excellent man pages and tasteful text-based tools, though - e.g. http://www.openbsd.org/faq/pf/example1.html#allrules is enough to configure a SOHO firewall.
Hmm, really? I love OpenBSD, but last I checked the installer tells you to create slices then drops you straight into fdisk. Has this been polished up? I'm just concerned "one of the easiest to install" would give a n00b the wrong impression.
I like to keep the manuals handy so that when I'm thinking about a problem I can compare them to Stevens and Kerrisk. Often it gives a new perspective. I didn't have the patience to get fast at developing in the environment.
So, how would you decribe what they've done? They found no trace of any backdoor whatsoever. The few parts that looked funny somehow have been rewritten in a more conservative manner, that's all.
http://www.openbsd.org/orders.html