* Connected to my site via TLSv1.2/ECDHE-ECDSA-AES256-GCM-SHA384
* Played a Youtube video just fine
* Was able to git and build libsodium, via the installed gcc 2.95.3
* wget'd an h.264 mp4 file and watched it via MediaPlayer
* OpenSSH 7.1 (newer Haiku ISOs may include a more recent release)
And the security model can't be helped if we want to maintain binary compatibility with BeOS - once we (mostly) drop that, we'll switch to something more sane in that department.
Awesome, that worked. Thanks!
It's also great to hear that Haiku will eventually improve the security model. That is its biggest weakness IMO, and removing it will open a lot of new doors.
Sorry if these are repetitive questions btw. I'm just curious.
The kernel already has moved pretty far forward. BeOS audio drivers, for instance, don't really work anymore in favor of our new multi-audio API (I don't think anyone had any use for BeOS audio drivers; we merged all the open-source ones, I think), the VFS layer has gotten major upgrades, we rewrote the thread scheduler and removed the 8-core limit we inherited from BeOS, and already have added ASLR and DEP support, among lots of other improvements. I think the only thing at this point which actually is still compatible kernel-wise are FS drivers (sorta) and graphics drivers (although of these, we have more in-tree than BeOS ever did, so I don't know if anyone even uses old BeOS ones anymore).