-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.1.6 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.1.6 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.14 released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.14 of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.3.1 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.3.1 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.2.2 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.2.2 of our open source
On 5/16/24 08:28, Neil Horman wrote:
Glad its working a bit better for you. If you are inclined, please feel
free to open a PR with your changes for review.
Well, the changes are *really* trivial. Necessary and trivial.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
librt.so.1 =>/lib/64/librt.so.1
> libstatomic.so.1 => /opt/bw/lib/libstatomic.so.1
> libc.so.1 => /lib/64/libc.so.1
> libmp.so.2 =>/lib/64/libmp.so.2
> libmd.so.1 =>/lib/64/libmd.so.1
> libscf.so.1 => /lib/64/
1
libgen.so.1 => /lib/64/libgen.so.1
libm.so.2 => /lib/64/libm.so.2
/lib/sparcv9/../libm/sparcv9/libm_hwcap1.so.2
/platform/SUNW,SPARC-Enterprise/lib/sparcv9/libc_psr.so.1
hubble $ /opt/bw/bin/openssl version
OpenSSL 3.3.0 9 Apr 2024 (Library: OpenSSL 3.3.0
a good
> result if I go with "no-quic" in the config :
>
> hubble $ $PERL ./Configure solaris64-sparcv9-cc \
> > --prefix=/opt/bw no-asm no-engine shared zlib-dynamic \
> > no-quic enable-weak-ssl-ciphers -DPEDANTIC 2>&1
> Confi
d I am able to get a good
result if I go with "no-quic" in the config :
hubble $ $PERL ./Configure solaris64-sparcv9-cc \
> --prefix=/opt/bw no-asm no-engine shared zlib-dynamic \
> no-quic enable-weak-ssl-ciphers -DPEDANTIC 2>&1
Configuring OpenSSL version 3.3.0 for target
PM Dennis Clarke via openssl-users
mailto:openssl-users@openssl.org>> wrote:
On 4/9/24 08:56, OpenSSL wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> OpenSSL version 3.3.0 released
> ==
On 5/12/24 21:42, Neil Horman wrote:
We added support for RCU locks in 3.3 which required the use of atomics (or
emulated atomic where they couldn't be supported), but those were in
libcrypro not liberal
I see. I am having great difficulty with 3.3 on an old Sun SPARC64
server where there
24 08:56, OpenSSL wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> >
> > OpenSSL version 3.3.0 released
> > ==
> >
>
>
> Trying to compile this on an old Solaris 10 machine and over
On 4/9/24 08:56, OpenSSL wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.3.0 released
==
Trying to compile this on an old Solaris 10 machine and over and over
and over I see these strange things as Undefined symbols
That is the master branch CHANGES.md. It will be synced later.
For the 3.1 changes please look at the CHANGES.md in the openssl-3.1
branch and/or inside the alpha tarball.
Tomas
On Thu, 2022-12-01 at 15:15 +, Kenneth Goldman wrote:
> The changes show a jump from 3.0 to 3.2
>
> https://githu
The changes show a jump from 3.0 to 3.2
https://github.com/openssl/openssl/blob/master/CHANGES.md
smime.p7s
Description: S/MIME cryptographic signature
t;
>>> On Dec 1, 2022, at 09:00, OpenSSL wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>>
>>>
>>> OpenSSL version 3.1 alpha 1 released
>>>
>>>
>>
t;
> -FG
>
>
> > On Dec 1, 2022, at 09:00, OpenSSL wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> >
> > OpenSSL version 3.1 alpha 1 released
> >
> >
> >
AFAICT, the migration guide doesn’t actually seem to mention upgrades to 3.1.
-FG
> On Dec 1, 2022, at 09:00, OpenSSL wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> OpenSSL version 3.1 alpha 1 released
>
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.1 alpha 1 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.1 is currently in alpha.
OpenSSL 3.1 alpha 1 has now been made available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1s released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1s of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.7 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.7 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.6 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.6 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1r released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1r of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 3.0.5 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.5 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 1.1.1q released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1q of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.4 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.4 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1p released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1p of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1o released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1o of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.3 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.3 of our open source
Hi,
Le 15/03/2022 à 23:49, Matt Caswell a écrit :
Those 2 links should be ok now. A problem with our scripts to flush
the CDN cache.
https://www.openssl.org/news/openssl-1.1.1-notes.html is updated, thanks !
but https://www.openssl.org/news/changelog.html#openssl-111 still shows
OpenSSL 1.1
On 15/03/2022 21:03, Michael Wojcik wrote:
From: openssl-users On Behalf Of Yann
Droneaud
Sent: Tuesday, 15 March, 2022 14:19
At the time of writing neither
https://www.openssl.org/news/openssl-1.1.1-notes.html nor
https://www.openssl.org/news/changelog.html#openssl-111 are updated to
match
Those 2 links should be ok now. A problem with our scripts to flush the
CDN cache.
Matt
On 15/03/2022 20:18, Yann Droneaud wrote:
Hi,
Le 15/03/2022 à 17:34, Matt Caswell a écrit :
OpenSSL version 1.1.1n released
===
OpenSSL - The Open Source toolkit
> From: openssl-users On Behalf Of Yann
> Droneaud
> Sent: Tuesday, 15 March, 2022 14:19
>
> At the time of writing neither
> https://www.openssl.org/news/openssl-1.1.1-notes.html nor
> https://www.openssl.org/news/changelog.html#openssl-111 are updated to
> match 1.1.1n release.
Neither have th
Hi,
Le 15/03/2022 à 17:34, Matt Caswell a écrit :
OpenSSL version 1.1.1n released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1n of our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1n released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1n of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.2 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.2 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0.1 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.1 of our open source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1m released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1m of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 3.0.0 released
==
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 3.0.0 of our open source
Hello OpenSSL Community,
Binary builds of OpenSSL version 1.1.1l for the HPE NonStop TNS/E (ia64) and
TNS/X (x86) platforms have been published on the
ITUGLIB website in its usual place at
https://ituglib.connect-community.org/apps/Ituglib/SrchOpenSrcLib.xhtml. The
builds consist
of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1l released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1l of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 beta 2 released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in beta.
OpenSSL 3.0 beta 2 has now been made available
However, I was wondering if anyone has ported/refactored the pkcs11
engine stuff for OpenSSL 3.0 already? is this on the TODO list for
the OpenSC/pkcs11 team? If I wanted to try to refactor the
opensc-pkcs11 module, how would I start?
PKCS #11 support is one (of many) possible items tha
Hi,
On 17/06/21 15:36, Matt Caswell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 beta 1 released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in beta
Steffen Nurpmeso wrote in
<20210617151209.s_znu%stef...@sdaoden.eu>:
|Matt Caswell wrote in
| <33db69e0-0f9b-c559-43f7-e5a2f85a4...@openssl.org>:
||On 17/06/2021 15:43, Steffen Nurpmeso wrote:
||> Fyi, i have $PERL5OPT=-C permanently in my environment, in
||> conjunction with LC_ALL=en_US.utf
Matt Caswell wrote in
<33db69e0-0f9b-c559-43f7-e5a2f85a4...@openssl.org>:
|On 17/06/2021 15:43, Steffen Nurpmeso wrote:
|> Fyi, i have $PERL5OPT=-C permanently in my environment, in
|> conjunction with LC_ALL=en_US.utf8 this results in the build error
|> as below. Prefixing LC_ALL=C fixes thi
7;master'
Your branch is up to date with 'origin/master'.
Configuring OpenSSL version 3.0.0-beta2-dev for target linux-x86_64
Using os-specific seed configuration
Creating configdata.pm
Running configdata.pm
Creating Makefile.in
syswrite() isn't allowed on :utf8 handl
Hello.
Matt Caswell wrote in
<20210617133633.ga24...@openssl.org>:
...
| OpenSSL version 3.0 beta 1 released
...
Congratulations after a lot of work!
Fyi, i have $PERL5OPT=-C permanently in my environment, in
conjunction with LC_ALL=en_US.utf8 this results in the build error
as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 beta 1 released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in beta.
OpenSSL 3.0 beta 1 has now been made available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 17 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 17 has now been made
My guess would be that OpenSSL is waiting for the system randomness
source to properly seed. This was an intentional change. Without it
security will likely be lost.
Paul Dale
On 6/5/21 8:34 pm, Sravani Maddukuri via openssl-users wrote:
Hi,
I have updated the openssl version running on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 16 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 16 has now been made
Hi,
I have updated the openssl version running on the switch from 1.1.1g to
1.1.1h and eventually to 1.1.1k.
Starting 1.1.1h, I am observing that the switch hangs for a significant
amount of time (> 3 minutes) when the call RAND_write_file is invoked from
the switch software.
The same c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 15 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 15 has now been made
e may be interested in the responses.
> I am getting the following warning while linking my app to openssl version
> 1.1.1k.
> Could you advise what can cause these warnings and how to resolve them?
> ../../../artifacts/openssl/arm3531/lib/libcrypto.a(async_posix.o): I
On 12/04/2021 21:52, Robert Smith via openssl-users wrote:
Hi,
I am getting the following warning while linking my app to openssl
version 1.1.1k. Could you advise what can cause these warnings and how
to resolve them? Thanks
It looks like your environment cannot support the async
Hi,
I am getting the following warning while linking my app to openssl version
1.1.1k. Could you advise what can cause these warnings and how to resolve them?
Thanks
../../../artifacts/openssl/arm3531/lib/libcrypto.a(async_posix.o): In function
`ASYNC_is_capable':
async_posix.c:(.text
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 14 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 14 has now been made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1k released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1k of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 13 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 13 has now been made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 12 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 12 has now been made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1j released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1j of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 3.0 alpha 11 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 11 has now been made
sl.org
> Cc: OpenSSL Announce ML ; OpenSSL User Support
> ML ; openssl-
> proj...@openssl.org
> Subject: Re: OpenSSL version 3.0.0-alpha10 published
>
> Please remove my email from your distribution
>
> > On Jan 7, 2021, at 9:08 AM, OpenSSL wrote:
> >
>
Please remove my email from your distribution
> On Jan 7, 2021, at 9:08 AM, OpenSSL wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> OpenSSL version 3.0 alpha 10 released
> =
>
> OpenSSL - The O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 10 released
=
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 10 has now been made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1i released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1i of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 9 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 9 has now been made available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 8 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 8 has now been made available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 7 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 7 has now been made available
> I think it would be better to just add a comment that the older branch
> changes are tracked elsewhere.
The note is already present, it's in the second paragraph of
https://www.openssl.org/news/changelog.html
but it is confusing nevertheless and it would be more useful if the
entire information
On Thu, 2020-09-24 at 07:01 +, Dr. Matthias St. Pierre wrote:
> > On 22/09/2020 15:03, Michael Wojcik wrote:
> > > changelog.html hasn't been updated since 1.1.1e.
> > >
> > > https://www.openssl.org/news/changelog.html#openssl-111 shows:
> >
> > That's the master Changelog. Confusing I know.
> On 22/09/2020 15:03, Michael Wojcik wrote:
> > changelog.html hasn't been updated since 1.1.1e.
> >
> > https://www.openssl.org/news/changelog.html#openssl-111 shows:
>
> That's the master Changelog. Confusing I know.
>
> The link to the 1.1.1 Changelog is at the top of the page.
It is indeed
On 22/09/2020 15:03, Michael Wojcik wrote:
> changelog.html hasn't been updated since 1.1.1e.
>
> https://www.openssl.org/news/changelog.html#openssl-111 shows:
That's the master Changelog. Confusing I know.
The link to the 1.1.1 Changelog is at the top of the page.
Matt
>
> -
> Open
changelog.html hasn't been updated since 1.1.1e.
https://www.openssl.org/news/changelog.html#openssl-111 shows:
-
OpenSSL 1.1.1
Changes between 1.1.1e and 1.1.1f [xx XXX ]
Changes between 1.1.1d and 1.1.1e [17 Mar 2020]
-
I noticed this because the Release Notes page
(https://www.op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1h released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
The OpenSSL project team is pleased to announce the release of
version 1.1.1h of our open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 6 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 6 has now been made available
e? Seems
>> not to have been uploaded to the key servers defined in my Enigmail.
>>
>>
>> On 7/16/20 9:48 AM, OpenSSL wrote:
>>> OpenSSL version 3.0 alpha 5 released
>>>
>>>
>>> OpenSSL - The Op
ed to the key servers defined in my Enigmail.
>
>
> On 7/16/20 9:48 AM, OpenSSL wrote:
> >
> > OpenSSL version 3.0 alpha 5 released
> >
> >
> > OpenSSL - The Open Source toolkit for SSL/TLS
> > https://w
Where can I get the PGP key for the signature for this message? Seems
not to have been uploaded to the key servers defined in my Enigmail.
On 7/16/20 9:48 AM, OpenSSL wrote:
>
> OpenSSL version 3.0 alpha 5 released
>
>
> OpenSSL -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
OpenSSL version 3.0 alpha 5 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 5 has now been made available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 4 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 4 has now been made available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 3 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 3 has now been made available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 alpha 2 released
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in alpha.
OpenSSL 3.0 alpha 2 has now been made available
On Thu, Apr 30, 2020 at 9:27 PM Richard Levitte wrote:
> Yes, running from the DESTDIR "installation" gets you into trouble.
> DESTDIR is intended to be a staging directory, i.e. a place to put
Fair enough, I don't have to use DESTDIR, I configure with openssldir
and prefix set to a sandbox now.
at 4:30 PM OpenSSL wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
>OpenSSL version 3.0 alpha 1 released
>
>
>OpenSSL - The Open Source toolkit for SSL/TLS
>https://www.openssl.org/
>
>OpenSSL 3.
On Fri, May 1, 2020 at 6:36 AM Richard Levitte wrote:
>
> On Sun, 26 Apr 2020 11:35:14 +0200,
> Yann Ylavic wrote:
> >
> > On Sun, Apr 26, 2020 at 12:15 AM Kurt Roeckx wrote:
> > >
> > > On Fri, Apr 24, 2020 at 01:26:05PM +0200, Yann Ylavic wrote:
> > > >
> > > > - DH_bits(dh) (used for logging o
build failed with the below.
>>
>> x86_64 Linux kernel 2.6.32
>> RHEL 6.7
>> Perl 5.10.1
>>
>> Everything through 1.1.1e was successful.
>>
>> ~~
>>
>>
>> ./config
>> Operating system: x86_64-whatever-linux2
>> Config
On Sun, 26 Apr 2020 11:35:14 +0200,
Yann Ylavic wrote:
>
> On Sun, Apr 26, 2020 at 12:15 AM Kurt Roeckx wrote:
> >
> > On Fri, Apr 24, 2020 at 01:26:05PM +0200, Yann Ylavic wrote:
> > >
> > > - DH_bits(dh) (used for logging only in httpd)
> > > Replaced by BN_num_bits(DH_get0_p(dh)).
> > > Not su
nal behaviour. OPENSSL_MODULES is of
particular interest in this case.
Suggested command to read a .pod file comfortably:
perldoc -o man doc/man7/openssl-env.pod
I suspect, btw, that people might wonder why we install provider modules
separately from engines. The simple reason is that they
On Fri, Apr 24, 2020 at 9:07 AM Nicola Tuveri wrote:
> At https://wiki.openssl.org/index.php/OpenSSL_3.0#Providers there was already
> an example of how to do this programmatically, and a link to the manpage for
> the config file syntax.
That's not working for me:
Failed to load Legacy provide
2, Ken Goldman wrote:
> > My build failed with the below.
> >
> > x86_64 Linux kernel 2.6.32
> > RHEL 6.7
> > Perl 5.10.1
> >
> > Everything through 1.1.1e was successful.
> >
> > ~~
> >
> >
> > ./config
> > Operating
6.7
> Perl 5.10.1
>
> Everything through 1.1.1e was successful.
>
> ~~
>
>
> ./config
> Operating system: x86_64-whatever-linux2
> Configuring OpenSSL version 3.0.0-alpha1 for target linux-x86_64
> Using os-specific seed configuration
> *** glibc detec
My build failed with the below.
x86_64 Linux kernel 2.6.32
RHEL 6.7
Perl 5.10.1
Everything through 1.1.1e was successful.
~~
./config
Operating system: x86_64-whatever-linux2
Configuring OpenSSL version 3.0.0-alpha1 for target linux-x86_64
Using os-specific seed configuration
*** glibc
On Sun, Apr 26, 2020 at 12:15 AM Kurt Roeckx wrote:
>
> On Fri, Apr 24, 2020 at 01:26:05PM +0200, Yann Ylavic wrote:
> >
> > - DH_bits(dh) (used for logging only in httpd)
> > Replaced by BN_num_bits(DH_get0_p(dh)).
> > Not sure this one should be deprecated, it seems to be used in several
> > pla
I would normally refrain but ...
On 25/04/2020 23:24, Salz, Rich via openssl-users wrote:
Yes, nice, why not reduce compile time and save prescious compiler
memory by getting rid of all-inline one-liners.
And link-time collapsing the identical code. I think this is an issue on some
Salz, Rich wrote in
<05c099a8-261f-43df-a59a-97ccf030f...@akamai.com>:
|>Yes, nice, why not reduce compile time and save prescious compiler
|memory by getting rid of all-inline one-liners.
|
|And link-time collapsing the identical code. I think this is an issue \
|on some Solaris, for
>Yes, nice, why not reduce compile time and save prescious compiler
memory by getting rid of all-inline one-liners.
And link-time collapsing the identical code. I think this is an issue on some
Solaris, for example.
> Sorry for coming
over sarcastic, i am listening to "This monkeys
On Fri, Apr 24, 2020 at 01:26:05PM +0200, Yann Ylavic wrote:
>
> - DH_bits(dh) (used for logging only in httpd)
> Replaced by BN_num_bits(DH_get0_p(dh)).
> Not sure this one should be deprecated, it seems to be used in several
> places in openssl codebase still, no replacement?
I think the replac
Hello Rich Salz,
Salz, Rich wrote in
:
|>I do not understand one thing at the moment. If i use
|no-deprecated then the stack handling is not available:
|
|If you use no-deprecated you have to use DEFINE_STACK_OF in exactly \
|one file. And use DECLARE_STACK in your common header fil
1 - 100 of 432 matches
Mail list logo
