I configured Openvpn server on ubuntu 16.04 and ubuntu was using a
old version of openssl 1.0.2 and I was updating openssl to v1.1.1
Now I've installed the openssl but now unable to mv file installed
to ln -s /usr/local/ssl/bin/openssl /usr/bin/openssl
failed to create symboli
to that
version and stop working if you remove it.
-Kyle H
On Tue, Nov 6, 2018, 14:02 Paul I configured Openvpn server on ubuntu 16.04 and ubuntu was using a old
> version of openssl 1.0.2 and I was updating openssl to v1.1.1
> Now I've installed the openssl but now unable to mv file installed
Thank you for the quick response
On Tue, Nov 6, 2018 at 4:42 PM Wim Lewis wrote:
>
> On 6. nóv. 2018, at 2:02 e.h., Paul wrote:
> > I configured Openvpn server on ubuntu 16.04 and ubuntu was using a old
> version of openssl 1.0.2 and I was updating openssl to v1.1.1
> &g
On 6. nóv. 2018, at 2:02 e.h., Paul wrote:
> I configured Openvpn server on ubuntu 16.04 and ubuntu was using a old
> version of openssl 1.0.2 and I was updating openssl to v1.1.1
> Now I've installed the openssl but now unable to mv file installed to ln -s
> /usr/local/ssl/bin/
I configured Openvpn server on ubuntu 16.04 and ubuntu was using a old
version of openssl 1.0.2 and I was updating openssl to v1.1.1
Now I've installed the openssl but now unable to mv file installed to ln -s
/usr/local/ssl/bin/openssl /usr/bin/openssl
failed to create symbolic link '/usr/bin
Salz, Rich via openssl-users wrote:
> It's hard enough for the openssl team to document the basic
> config/build things, let alone all the operating systems and
> vendor-supplied stuff.
> Perhaps a wiki page, that the community could help maintain?
that's what I had in mind.
--
Thanks Uri.
On the Homebrew side the same sort of loose plan is being followed. I
recently departed the project for unrelated reasons but before I left I
was pushing a timetable of no later than Summer 2019 to have migrated
everything over to OpenSSL 1.1.1, likely with some package-availability
On 9/20/18, 4:39 PM, "openssl-users on behalf of Viktor Dukhovni"
wrote:
Despite (IMHO) its increasing obsolescence and irrelevance, the LibreSSL
fork of OpenSSL 1.0.2 also supports ECDSA.
Yep.
> so openssl 1.1.0 or newer, and his Mac is infested with
> 0.98letter.
> On Sep 20, 2018, at 3:43 PM, Michael Richardson wrote:
>
> Sitting with a colleague, he's trying to get some code working that requires
> ECDSA support,
ECDSA support is also present in OpenSSL 1.0.2. With recent versions of
MacOS you actually get LibreSSL with the base system:
$
Macports team is working on upgrading OpenSSL to 1.1.1. It takes time because
they plan to move all the ports that depend on OpenSSL to that level. I assume
that once that is done, 1.0.2 won't be supported/available on Macports anymore.
Installation - as Dominyk said: "sudo port install
FWIW on macOS:
If you use Homebrew and want/need OpenSSL 1.1.1 then `brew install
openssl@1.1`. If you want the 1.0.2x series `brew install openssl`
currently is & will likely remain attached to 1.0.2x for the foreseeable.
If you use MacPorts and want OpenSSL 1.0.2x then `sudo port install
It's hard enough for the openssl team to document the basic config/build
things, let alone all the operating systems and vendor-supplied stuff.
Perhaps a wiki page, that the community could help maintain?
--
openssl-users mailing list
To unsubscribe:
(I'm a Linux desktop guy)
Sitting with a colleague, he's trying to get some code working that requires
ECDSA support, so openssl 1.1.0 or newer, and his Mac is infested with
0.98letter.
There are a a whole bunch of pages with a variety of recommendations.
None of them are on openssl.org... I
On 21-06-2010 20:37, Tran, Brandon D, CTR, OSD-CAPE wrote:
I have couple questions.
1) How do I know if openssl running on the solaris 9 10 boxes.
(openssl is installed-pkginfo –i)
The command
$ openssl version
should tell you what version of the openssl utility and library
you have (if
A version bump usually indicates an ABI difference, which means that
you're best using 0.9.7i for the programs using 0.9.7, and use 0.9.8a
for programs using the later interface.
On 3/18/06, Hector Santos [EMAIL PROTECTED] wrote:
I have multiple applications using OPENSSL 0.9.7c and I'm finally
In message [EMAIL PROTECTED] on Sat, 18 Mar 2006 02:27:18 -0500, Hector
Santos [EMAIL PROTECTED] said:
ssluser I have multiple applications using OPENSSL 0.9.7c and I'm finally
getting
ssluser around to updating it.
ssluser
ssluser I have downloaded and recompiled the *eay*.dll files for:
Richard Levitte - VMS Whacker wrote:
In message [EMAIL PROTECTED] on Sat, 18 Mar 2006 02:27:18 -0500, Hector Santos
[EMAIL PROTECTED] said:
ssluser I have multiple applications using OPENSSL 0.9.7c and I'm finally
getting
ssluser around to updating it.
ssluser
ssluser Can I just use the new
Thanks Richard, Bill and et.
I didn't see a straight forward document saying if the prototypes or
structures changed in 0.9.8a, but part of the reason to do the update
(besides security issues) was that I am starting on a new project that
requires the EVP_SHA256 function and when I first compiled
On Sat, Mar 18, 2006 at 02:00:16PM -0500, Hector Santos wrote:
Thanks Richard, Bill and et.
I didn't see a straight forward document saying if the prototypes or
structures changed in 0.9.8a, but part of the reason to do the update
(besides security issues) was that I am starting on a new
I have multiple applications using OPENSSL 0.9.7c and I'm finally getting
around to updating it.
I have downloaded and recompiled the *eay*.dll files for:
0.9.7i
0.9.8a
Can I just use the new DLLs for 0.9.8a or do I need to recompile my
applications? I take it I will be fine with
20 matches
Mail list logo
