Could you point me to some of the current changes that have made the system buggy? If HardenedBSD's features do introduce bugs, they should be fixed.
HardenedBSD has never been defunct or inactive.
HardenedBSD has per-application and per-jail exploit mitigation toggles. If an application violates an active exploit mitigation, the user can choose to either go without the application or disable the exploit…
HardenedBSD still uses LibreSSL in base. The switch back to OpenSSL will be on 01 July 2018, as mentioned in the article you linked to.
HardenedBSD currently follows upstream FreeBSD with regards to in-kernel crypto.
Could you point me to some of the current changes that have made the system buggy? If HardenedBSD's features do introduce bugs, they should be fixed.
HardenedBSD has never been defunct or inactive.
HardenedBSD has per-application and per-jail exploit mitigation toggles. If an application violates an active exploit mitigation, the user can choose to either go without the application or disable the exploit…
HardenedBSD still uses LibreSSL in base. The switch back to OpenSSL will be on 01 July 2018, as mentioned in the article you linked to.
HardenedBSD still uses LibreSSL in base. The switch back to OpenSSL will be on 01 July 2018, as mentioned in the article you linked to.
HardenedBSD currently follows upstream FreeBSD with regards to in-kernel crypto.