Github messages for voidlinux
 help / color / mirror / Atom feed
From: agausmann <agausmann@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: openssl-1.1.1f
Date: Sat, 18 Apr 2020 09:13:56 +0200	[thread overview]
Message-ID: <20200418071356.QQ-9pY3eNrYW1w1ABes4OGs-dEWLPi4XuYeVTjwj8Mo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21056@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

New comment by agausmann on void-packages repository

https://github.com/void-linux/void-packages/pull/21056#issuecomment-615653879

Comment:
> LibreSSL used to "provide" OpenSSL

Isn't this still the case? Their [latest release notes](https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.1.0-relnotes.txt) explicitly mention compatibility with OpenSSL 1.1.1.

I thought Void explicitly uses LibreSSL instead, what happened? From the [homepage](https://voidlinux.org):

> We were the first distribution to switch to LibreSSL by default, replacing OpenSSL.
>
> Due to the Heartbleed fiasco, we believe that the OpenBSD project has qualified and pro-active developers to provide a more secure alternative.

  parent reply	other threads:[~2020-04-18  7:13 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 13:51 [PR PATCH] " Johnnynator
2020-04-18  7:13 ` agausmann
2020-04-18  7:13 ` agausmann [this message]
2020-04-18  7:44 ` flexibeast
2020-04-18  7:55 ` agausmann
2020-04-18  7:56 ` agausmann
2020-04-21 22:26 ` xtraeme
2020-04-22  1:14 ` [PR PATCH] [Updated] " Johnnynator
2020-04-23  7:38 ` travankor
2021-02-10 22:56 ` [PR PATCH] [Updated] " Johnnynator
2021-02-13 20:21 ` Johnnynator
2021-02-13 21:05 ` Johnnynator
2021-02-13 23:24 ` Johnnynator
2021-02-15 15:30 ` Johnnynator
2021-02-17 19:20 ` Johnnynator
2021-02-17 21:41 ` Johnnynator
2021-02-17 22:33 ` Johnnynator
2021-02-18 19:54 ` Johnnynator
2021-02-18 20:25 ` [PR PATCH] [Updated] New package: openssl-1.1.1j Johnnynator
2021-02-20 13:25 ` Johnnynator
2021-02-21 18:38 ` Johnnynator
2021-02-21 21:05 ` Johnnynator
2021-02-21 21:09 ` Johnnynator
2021-02-21 21:14 ` [PR PATCH] [Updated] " Johnnynator
2021-02-21 21:49 ` ericonr
2021-02-22 20:39 ` [PR PATCH] [Updated] " Johnnynator
2021-02-22 21:51 ` Johnnynator
2021-02-23 19:22 ` Johnnynator
2021-02-23 22:57 ` Johnnynator
2021-02-24 17:46 ` ericonr
2021-02-24 17:59 ` ericonr
2021-02-24 18:03 ` Johnnynator
2021-02-24 18:05 ` Johnnynator
2021-02-24 18:08 ` ericonr
2021-02-24 18:13 ` Johnnynator
2021-02-24 18:13 ` ericonr
2021-02-24 18:13 ` ericonr
2021-02-24 18:14 ` Johnnynator
2021-02-24 18:15 ` ericonr
2021-02-24 18:16 ` Johnnynator
2021-02-24 18:16 ` Johnnynator
2021-02-24 18:21 ` Johnnynator
2021-02-24 18:21 ` Johnnynator
2021-02-24 18:24 ` Johnnynator
2021-02-24 18:30 ` Johnnynator
2021-02-24 18:30 ` Johnnynator
2021-02-24 18:33 ` Johnnynator
2021-02-24 18:36 ` [PR PATCH] [Updated] " Johnnynator
2021-02-24 18:37 ` Johnnynator
2021-02-24 18:56 ` Johnnynator
2021-02-25 20:19 ` [PR PATCH] [Updated] " Johnnynator
2021-02-26 21:30 ` Johnnynator
2021-02-28 16:23 ` Johnnynator
2021-02-28 23:43 ` Johnnynator
2021-03-01  7:07 ` fosslinux
2021-03-01  8:54 ` Johnnynator
2021-03-01  8:56 ` [PR PATCH] [Updated] " Johnnynator
2021-03-01 10:40 ` Johnnynator
2021-03-02 19:35 ` ericonr
2021-03-02 19:37 ` ericonr
2021-03-02 19:39 ` ericonr
2021-03-02 19:42 ` ericonr
2021-03-02 19:59 ` ericonr
2021-03-02 20:04 ` [PR PATCH] [Updated] " Johnnynator
2021-03-04 21:43 ` Johnnynator
2021-03-04 22:37 ` Johnnynator
2021-03-04 23:05 ` Johnnynator
2021-03-04 23:53 ` Johnnynator
2021-03-05 18:21 ` Johnnynator
2021-03-06  3:21 ` ericonr
2021-03-06  3:21 ` [PR PATCH] [Closed]: " ericonr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200418071356.QQ-9pY3eNrYW1w1ABes4OGs-dEWLPi4XuYeVTjwj8Mo@z \
    --to=agausmann@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).