Comments on: LibreSSL not just available but default https://www.dragonflydigest.com/2016/10/19/libressl-not-just-available-but-default/ A running description of activity related to DragonFly BSD. Fri, 28 Oct 2016 00:34:35 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Vote4BSD | BSD Now 165 | Jupiter Broadcasting https://www.dragonflydigest.com/2016/10/19/libressl-not-just-available-but-default/comment-page-1/#comment-482253 Fri, 28 Oct 2016 00:34:35 +0000 https://www.dragonflydigest.com/?p=18794#comment-482253 […] LibreSSL not just available but default (DragonFlyBSD) […]

]]> By: Anonymous https://www.dragonflydigest.com/2016/10/19/libressl-not-just-available-but-default/comment-page-1/#comment-476850 Thu, 20 Oct 2016 05:20:50 +0000 https://www.dragonflydigest.com/?p=18794#comment-476850 Congrats to the Dragonfly team! OpenSSL was/is a nightmare.

]]> By: John https://www.dragonflydigest.com/2016/10/19/libressl-not-just-available-but-default/comment-page-1/#comment-476726 Thu, 20 Oct 2016 01:22:17 +0000 https://www.dragonflydigest.com/?p=18794#comment-476726 This was misunderstood.
ALL the base has used LibreSSL for several weeks. This was hardcoded; there was no way to avoid it. The “optional” part was to continue to build OpenSSL, which nothing in base used. OpenSSL continued to build unless make.conf was configured to stop it.

What has changed is now OpenSSL doesn’t build unless make.conf is configured to build it.

The writeup should be modified because it’s misleading as written.

]]>