OpenBSD 6.2 Released (openbsd.org)
basscomm writes: OpenBSD 6.2 has now been released. Check out the release notes if you're into that kind of thing. Some of the new features and systems include improved hardware support, vmm(4)/ vmd(8) improvements, IEEE 802.11 wireless stack improvements, generic network stack improvements, installer improvements, routing daemons and other userland network improvements, security improvements and more. Here is the full list of changes.
The *BSDs are quickly rendering Linux irrelevant, especially now that nearly all Linux distros have started using systemd which has caused stability and reliability problems for lots of users.
OpenBSD is proving to be an excellent server OS. Its focus on security is more important now than ever before.
FreeBSD is proving to be an excellent general-purpose OS. It can be used very successfully on servers, as well as on workstations. It probably has the best hardware support of all of the BSDs, and its ZFS support is remarkably useful.
NetBSD is proving to be an excellent embedded OS. It supports a huge range of systems, both new and ancient.
DragonFly BSD is proving to be an excellent testbed for next-generation technologies. Its HAMMER filesystem is superb, and it has long had excellent support for multi-CPU systems, and its virtual kernel support is extraordinarily useful.
It's getting to the point where Linux really doesn't offer any substantial benefits over the *BSDs. In many ways the *BSDs offer significant advantages over Linux.
The *BSDs are becoming the go-to operating system for a wide range of computing needs, from servers to workstations to embedded systems.
> And even security would be a bit better 'out of the box' :)
No. It won't Because OpenBSD refuses the concept of "layered protectoin", every user has the run of every component of the operating system that other users have failed to individually secure. And I *love* stealing unprotected SSH keys, because Theo de Raadt insists that "if your box isn't secure, you shouldn't have one", and refuses to permit a change to ssh-keygen to *stop* generating unencrypted SSH keys by default.
I particularly enjoy stealing them from CIFS and NFS shares and backups, because even if the OpenBSD box is "secure", people inevitably leave those convenient passphrase keys lying around. It's almost as fun as stealing Subversion keys for Sourceforge hosted source code.
Just for the record, this AC is full of shit.
ssh-keygen doesn't generate unencrypted ssh keys by default, that only happens when you skip entering a passphrase (same behavior as ssh-keygen on literally any other platform, because - who knew - it actually originates from OpenBSD). If you do enter a passphrase, it will even refuse to generate a key if the passphrase is too short.
As for layered security, there's plenty of that in OpenBSD, a good deal of which other OSs do not have. Most recent example would be the "pledge" system call (formerly known as "tame").
I particularly enjoy stealing them from CIFS and NFS shares and backups, because even if the OpenBSD box is "secure", people inevitably leave those convenient passphrase keys lying around.
Aha, the "passphrase keys". For the record, as anything else, the private key is created chmod 600. You're not "stealing" shit, you're making things up.
CLI paste? paste.pr0.tips!