The switch to from OpenSSL to LibreSSL in DragonFly’s base and in dports has led to more cleanup, including the removal of an old, strange munitions/crypto import restriction. Be careful upgrading if you’re on master, though!
Remember I posted that LibreSSL is in base DragonFly, but not default? Well, it’s default now. You can have a system without OpenSSL at all, by rebuilding DragonFly-current and using up-to-date dports.
Update: see John’s comments for clarification: LibreSSL is default; the change is that OpenSSL isn’t even built any more. The result is still the same good news: you can have an OpenSSL-free DragonFly system now.
I don’t have it uploaded yet, but DragonFly 4.6.1 is tagged. Anyone with an existing 4.6.0 or earlier system can upgrade now. Use the 4.6 release instructions if you are unsure on how to upgrade. The 4.6.1 tag commit message has all the changes.
If you had trouble getting your laptop’s touchpad to work under DragonFly, try again. (If you are running DragonFly-current)
It’s now possible to build dports using LibreSSL instead of OpenSSL. Set SSL_DEFAULT in make.conf to the appropriate port name, and start building. Use synth for fastest results, of course.
LibreSSL will eventually become the default library. This is in addition to the previously-mentioned, already-completed in DragonFly 4.7, base system switch to LibreSSL.
Matthew Dillon has added powerd, a utility that will automatically step down processor speed based on reported temperature. The range is configurable, and there’s some other nice-to-have features. This will save your CPU from melting, and probably also your thighs from being burned.
Recent changes for virtual machine support and the new powerd utility have been rolled into the release branch for DragonFly. They’ll probably be in the next point release, or you can rebuild a release machine now for immediate access.
Also mentioned in the update from Matthew Dillon, DragonFly-master users should upgrade carefully as DragonFly migrates to using LibreSSL in base, and dports-based LibreSSL in dports.
If you are on DragonFly-current, AKA DragonFly 4.7, make sure to perform a full buildworld on your next upgrade. Tomohiro Kusumi changed a Hammer ioctl, and the buildworld is needed to keep everything in sync.
The last bits of Linux emulation have been removed from DragonFly. It’s 32-bit, so it’s been unsupported since DragonFly went to 64-bit only with the 4.0 release. Also, some other 32-bit only items are gone, including the cs, ep, ex, fe, and vx network drivers. It’s almost impossible that anyone was using it, but it’s notable because that’s some… 15-20k lines of code gone? Removal of unused code is also positive.
Because this always happens just after I create a DragonFly release, there’s a new version of OpenSSL. However, this is for version 1.0.2. 1.0.1 is what’s in the release, and it’s supported through the end of the year.
OpenSSH has a major version bump in DragonFly, to 7.3p1. This means some features – specifically patches for High Performance Networking – are no longer there, and you’ll get an error if your config file requires them. Either remove the options from your config, or install OpenSSH from dports.