The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing anumber of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing a
It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and packagesavailable.
On Wednesday, June 22, 2022 at 2:42:27 p.m. UTC-4, Randall wrote:number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing a
available.It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and packages
I am trying a new build technique for 1.1. Instead of running each build it its own job, all builds will run in one pipeline. This should significantly improve checkout speed, which is the bottleneck on our J-series machine. The L-series OSSNS processis significantly faster but even with that, checkout is still the rate-limiting step for OpenSSL builds. There are over 20000 files in the repository, so that is a big checkout. More to come. We probably will push the L-series builds to the ITUGLIB
On Monday, June 27, 2022 at 11:33:56 a.m. UTC-4, Randall wrote:number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
On Wednesday, June 22, 2022 at 2:42:27 p.m. UTC-4, Randall wrote:
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing a
available.It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and packages
is significantly faster but even with that, checkout is still the rate-limiting step for OpenSSL builds. There are over 20000 files in the repository, so that is a big checkout. More to come. We probably will push the L-series builds to the ITUGLIBI am trying a new build technique for 1.1. Instead of running each build it its own job, all builds will run in one pipeline. This should significantly improve checkout speed, which is the bottleneck on our J-series machine. The L-series OSSNS process
We are currently having some heating/cooling issues and as a result the ITUGLIB website might not be available temporarily. If you urgently need to build OpenSSL 3.0.4, please clone it from https://github.com/openssl/openssl.git or download the tarballfrom https://www.openssl.org/source/. For OpenSSL 1.1.1p, clone from https://github.com/ituglib/openssl.git and use the ituglib_release branch or OpenSSL_1_1_1p_NSK tag. Running ./Configure should give you the appropriate build, but the normal builds for
On 6/27/2022 3:13 PM, Randall wrote:number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
On Monday, June 27, 2022 at 11:33:56 a.m. UTC-4, Randall wrote:
On Wednesday, June 22, 2022 at 2:42:27 p.m. UTC-4, Randall wrote:
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing a
available.It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and packages
process is significantly faster but even with that, checkout is still the rate-limiting step for OpenSSL builds. There are over 20000 files in the repository, so that is a big checkout. More to come. We probably will push the L-series builds to theI am trying a new build technique for 1.1. Instead of running each build it its own job, all builds will run in one pipeline. This should significantly improve checkout speed, which is the bottleneck on our J-series machine. The L-series OSSNS
tarball from https://www.openssl.org/source/. For OpenSSL 1.1.1p, clone from https://github.com/ituglib/openssl.git and use the ituglib_release branch or OpenSSL_1_1_1p_NSK tag. Running ./Configure should give you the appropriate build, but the normalWe are currently having some heating/cooling issues and as a result the ITUGLIB website might not be available temporarily. If you urgently need to build OpenSSL 3.0.4, please clone it from https://github.com/openssl/openssl.git or download the
Is it even worth it to deal with 3.0.4, since 3.0.5 is coming out to fix
a data corruption issue (that could lead to remote execution)?
Granted, the issue is with code that uses AVX512, and I'm not sure that
the L-Series release does use AVX512 (haven't looked recently).
On Tuesday, June 28, 2022 at 11:55:45 a.m. UTC-4, red floyd wrote:a number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
On 6/27/2022 3:13 PM, Randall wrote:
On Monday, June 27, 2022 at 11:33:56 a.m. UTC-4, Randall wrote:
On Wednesday, June 22, 2022 at 2:42:27 p.m. UTC-4, Randall wrote:
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing
available.It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and packages
process is significantly faster but even with that, checkout is still the rate-limiting step for OpenSSL builds. There are over 20000 files in the repository, so that is a big checkout. More to come. We probably will push the L-series builds to theI am trying a new build technique for 1.1. Instead of running each build it its own job, all builds will run in one pipeline. This should significantly improve checkout speed, which is the bottleneck on our J-series machine. The L-series OSSNS
tarball from https://www.openssl.org/source/. For OpenSSL 1.1.1p, clone from https://github.com/ituglib/openssl.git and use the ituglib_release branch or OpenSSL_1_1_1p_NSK tag. Running ./Configure should give you the appropriate build, but the normalWe are currently having some heating/cooling issues and as a result the ITUGLIB website might not be available temporarily. If you urgently need to build OpenSSL 3.0.4, please clone it from https://github.com/openssl/openssl.git or download the
Is it even worth it to deal with 3.0.4, since 3.0.5 is coming out to fix
a data corruption issue (that could lead to remote execution)?
Granted, the issue is with code that uses AVX512, and I'm not sure that the L-Series release does use AVX512 (haven't looked recently).I don't have a date on 3.0.5 as of yet. 3.0.3 was skipped due to compile problems. Your choice really.
Regards,
Randall
On Tuesday, June 28, 2022 at 3:17:06 p.m. UTC-4, Randall wrote:failing a number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More
On Tuesday, June 28, 2022 at 11:55:45 a.m. UTC-4, red floyd wrote:
On 6/27/2022 3:13 PM, Randall wrote:
On Monday, June 27, 2022 at 11:33:56 a.m. UTC-4, Randall wrote:
On Wednesday, June 22, 2022 at 2:42:27 p.m. UTC-4, Randall wrote:
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is
packages available.It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and
process is significantly faster but even with that, checkout is still the rate-limiting step for OpenSSL builds. There are over 20000 files in the repository, so that is a big checkout. More to come. We probably will push the L-series builds to theI am trying a new build technique for 1.1. Instead of running each build it its own job, all builds will run in one pipeline. This should significantly improve checkout speed, which is the bottleneck on our J-series machine. The L-series OSSNS
tarball from https://www.openssl.org/source/. For OpenSSL 1.1.1p, clone from https://github.com/ituglib/openssl.git and use the ituglib_release branch or OpenSSL_1_1_1p_NSK tag. Running ./Configure should give you the appropriate build, but the normalWe are currently having some heating/cooling issues and as a result the ITUGLIB website might not be available temporarily. If you urgently need to build OpenSSL 3.0.4, please clone it from https://github.com/openssl/openssl.git or download the
Is it even worth it to deal with 3.0.4, since 3.0.5 is coming out to fix a data corruption issue (that could lead to remote execution)?
Hi All,Granted, the issue is with code that uses AVX512, and I'm not sure that the L-Series release does use AVX512 (haven't looked recently).I don't have a date on 3.0.5 as of yet. 3.0.3 was skipped due to compile problems. Your choice really.
Regards,
Randall
FYI: The 3.0.4 and 1.1.1p releases for OpenSSL on L-series are now on the ITUGLIB website. J-series to follow in the next few days.
Regards,
Randall
On 6/27/2022 3:13 PM, Randall wrote:number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
On Monday, June 27, 2022 at 11:33:56 a.m. UTC-4, Randall wrote:
On Wednesday, June 22, 2022 at 2:42:27 p.m. UTC-4, Randall wrote:
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing a
available.It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and packages
process is significantly faster but even with that, checkout is still the rate-limiting step for OpenSSL builds. There are over 20000 files in the repository, so that is a big checkout. More to come. We probably will push the L-series builds to theI am trying a new build technique for 1.1. Instead of running each build it its own job, all builds will run in one pipeline. This should significantly improve checkout speed, which is the bottleneck on our J-series machine. The L-series OSSNS
tarball from https://www.openssl.org/source/. For OpenSSL 1.1.1p, clone from https://github.com/ituglib/openssl.git and use the ituglib_release branch or OpenSSL_1_1_1p_NSK tag. Running ./Configure should give you the appropriate build, but the normalWe are currently having some heating/cooling issues and as a result the ITUGLIB website might not be available temporarily. If you urgently need to build OpenSSL 3.0.4, please clone it from https://github.com/openssl/openssl.git or download the
Is it even worth it to deal with 3.0.4, since 3.0.5 is coming out to fix
a data corruption issue (that could lead to remote execution)?
Granted, the issue is with code that uses AVX512, and I'm not sure that
the L-Series release does use AVX512 (haven't looked recently).
On 6/27/2022 3:13 PM, Randall wrote:number of tests including hard-looping/stack corruption of anything relating to the BN subset of cryptographic algorithms. I am looking into the cause but are not currently expecting that this patch will be made available or recommended. More to come...
On Monday, June 27, 2022 at 11:33:56 a.m. UTC-4, Randall wrote:
On Wednesday, June 22, 2022 at 2:42:27 p.m. UTC-4, Randall wrote:
On Tuesday, June 21, 2022 at 9:58:49 p.m. UTC-4, Randall wrote:
The ITUGLIB team is currently involved in build/test of OpenSSL 1.1.1p and 3.0.4. As of now, we are having a lot of success with 3.0.4 and it should show up on the website some time tomorrow. The 1.1.1p build, however, has issues and is failing a
available.It turns out that the test suite does not like running without verbose mode. At this point, only the ecparam test is failing, which is the same as 1.1.1o, so things are looking better. I will update when the test cycles are all done and packages
process is significantly faster but even with that, checkout is still the rate-limiting step for OpenSSL builds. There are over 20000 files in the repository, so that is a big checkout. More to come. We probably will push the L-series builds to theI am trying a new build technique for 1.1. Instead of running each build it its own job, all builds will run in one pipeline. This should significantly improve checkout speed, which is the bottleneck on our J-series machine. The L-series OSSNS
tarball from https://www.openssl.org/source/. For OpenSSL 1.1.1p, clone from https://github.com/ituglib/openssl.git and use the ituglib_release branch or OpenSSL_1_1_1p_NSK tag. Running ./Configure should give you the appropriate build, but the normalWe are currently having some heating/cooling issues and as a result the ITUGLIB website might not be available temporarily. If you urgently need to build OpenSSL 3.0.4, please clone it from https://github.com/openssl/openssl.git or download the
Is it even worth it to deal with 3.0.4, since 3.0.5 is coming out to fix
a data corruption issue (that could lead to remote execution)?
Granted, the issue is with code that uses AVX512, and I'm not sure that
the L-Series release does use AVX512 (haven't looked recently).
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 714 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 141:20:13 |
| Calls: | 12,087 |
| Files: | 14,998 |
| Messages: | 6,517,442 |