Date: Mon, 4 Mar 2019 09:04:31 -0700 From: "@lbutlr" <kremels@kreme.com> To: freebsd-questions@freebsd.org Subject: Re: OpenSSL111 Message-ID: <684E88FA-DA55-47FB-9D14-1028FE5F88CD@kreme.com> In-Reply-To: <CAAdA2WMNOq3CWx%2BJ8gHPW6whsRuhp5zeLA3KvGurqTHcaRq9qw@mail.gmail.com> References: <BAC79191-8F7B-4A9D-99AE-6D8FD7281693@kreme.com> <CAAdA2WMNOq3CWx%2BJ8gHPW6whsRuhp5zeLA3KvGurqTHcaRq9qw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03 Mar 2019, at 02:40, Odhiambo Washington <odhiambo@gmail.com> = wrote: > On Sat, 2 Mar 2019 at 21:46, @lbutlr <kremels@kreme.com> wrote: >> What is the current port status of moving to OpenSSL111 over 1.0.2r? >=20 > There is /usr/ports/security/openssl111/ That isn=E2=80=99t at all relevant to my question though. I=E2=80=99m = not asking about OpenSSL 1.1.1, I=E2=80=99m asking about the status of = ports moving to it (since it cannot co-exist with 1.0.2) >> Is there an easy way to check if any ports I have are still not able = to >> use OpenSSL 1.1.1? >=20 > Since you install the ports yourself, you must check with their = respective > support channels/mailing lists to > know how they interact with or support ver.111. That's what I think as = a > Sysadmin. > It also depends on why you really need ver111 =F0=9F=98=83 Since 1.0.2 has an EOL date of December and some ports are no longer = supporting it it would be useful to know what the progress is for the = ports tree the than checking dozens (or hundred) of individual packages. --=20 Does the name Pavlov ring a bell?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?684E88FA-DA55-47FB-9D14-1028FE5F88CD>