RE: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376
Thank you, Mr. Roeckx. J.J. Clemmer -Original Message- From: Kurt Roeckx via RT [mailto:r...@openssl.org] Sent: Saturday, June 28, 2014 2:43 PM To: Clemmer, John J CIV (US) Cc: openssl-dev@openssl.org Subject: Re: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376 On Sat, Jun 28, 2014 at 05:21:40PM +0200, Clemmer, John J CIV via RT wrote: > OpenSSL Development Team, > > My attempts to compile OpenSSL v.1.0.0m on the day of its release as well as > last night both resulted in the same error, whereby INT_MAX is used before it > is declared in ssl/s3_pkt.c on line 586. The problem is solved. There just wasn't a released with the fix yet. Kurt
RE: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376
Thanks, for your reply Dr. Henson. I'll stick with the hourly snapshots from now on. J. Jeff Clemmer IT Specialist Phone: 434-980-7525 Email: john.j.clemmer4@mail.mil -Original Message- From: Stephen Henson via RT [mailto:r...@openssl.org] Sent: Saturday, June 28, 2014 1:58 PM To: Clemmer, John J CIV (US) Cc: openssl-dev@openssl.org Subject: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376 On Sat Jun 28 17:21:39 2014, john.j.clemmer4@mail.mil wrote: > OpenSSL Development Team, > > My attempts to compile OpenSSL v.1.0.0m on the day of its release as > well as last night both resulted in the same error, whereby INT_MAX is > used before it is declared in ssl/s3_pkt.c on line 586. > > Researching this error, I found a discussion among some of your > developers, who experienced the same issue during their own > compilation attempts. They created a bug report at > http://rt.openssl.org/Ticket/Display.html?id=3376. The ticket was > marked as resolved on 5.6.2014; however, I again downloaded the source > from openssl.org last night and examined ssl/s3_pkt.c. I observed that > the limits.h include statement is still omitted, thus producing the > compilation error. > The source of a specific version of OpenSSL does not change. So it's not surprising that the bug is still in 1.0.0m When a bug is fixed it will normally appear in the next release. There hasn't been one since 1.0.0.m so the fix isn't in an official release yet. Before then you can download nightly snapshots which will include the fix or obtain sources from the git repository. See: https://www.openssl.org/source/ Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org :��I"Ϯ��r�m (Z+�7�zZ)���1���x��hW^��^��%�� ��&jם.+-1�ځ��j:+v���h�
RE: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376
Thank you, Mr. Roeckx. J.J. Clemmer -Original Message- From: Kurt Roeckx via RT [mailto:r...@openssl.org] Sent: Saturday, June 28, 2014 2:43 PM To: Clemmer, John J CIV (US) Cc: openssl-dev@openssl.org Subject: Re: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376 On Sat, Jun 28, 2014 at 05:21:40PM +0200, Clemmer, John J CIV via RT wrote: > OpenSSL Development Team, > > My attempts to compile OpenSSL v.1.0.0m on the day of its release as well as > last night both resulted in the same error, whereby INT_MAX is used before it > is declared in ssl/s3_pkt.c on line 586. The problem is solved. There just wasn't a released with the fix yet. Kurt __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
RE: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376
Thanks, for your reply Dr. Henson. I'll stick with the hourly snapshots from now on. J. Jeff Clemmer IT Specialist Phone: 434-980-7525 Email: john.j.clemmer4@mail.mil -Original Message- From: Stephen Henson via RT [mailto:r...@openssl.org] Sent: Saturday, June 28, 2014 1:58 PM To: Clemmer, John J CIV (US) Cc: openssl-dev@openssl.org Subject: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376 On Sat Jun 28 17:21:39 2014, john.j.clemmer4@mail.mil wrote: > OpenSSL Development Team, > > My attempts to compile OpenSSL v.1.0.0m on the day of its release as > well as last night both resulted in the same error, whereby INT_MAX is > used before it is declared in ssl/s3_pkt.c on line 586. > > Researching this error, I found a discussion among some of your > developers, who experienced the same issue during their own > compilation attempts. They created a bug report at > http://rt.openssl.org/Ticket/Display.html?id=3376. The ticket was > marked as resolved on 5.6.2014; however, I again downloaded the source > from openssl.org last night and examined ssl/s3_pkt.c. I observed that > the limits.h include statement is still omitted, thus producing the > compilation error. > The source of a specific version of OpenSSL does not change. So it's not surprising that the bug is still in 1.0.0m When a bug is fixed it will normally appear in the next release. There hasn't been one since 1.0.0.m so the fix isn't in an official release yet. Before then you can download nightly snapshots which will include the fix or obtain sources from the git repository. See: https://www.openssl.org/source/ Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376
https://www.openssl.org/news/openssl-1.0.0-notes.html *Known issues in OpenSSL 1.0.0m:* * EAP-FAST and other applications using tls_session_secret_cb wont resume sessions. Fixed in 1.0.0n-dev * Compilation failure of s3_pkt.c on some platforms due to missing include. Fixed in 1.0.0n-dev Cheers Jan Am 28.06.2014 17:21, schrieb Clemmer, John J CIV via RT: OpenSSL Development Team, My attempts to compile OpenSSL v.1.0.0m on the day of its release as well as last night both resulted in the same error, whereby INT_MAX is used before it is declared in ssl/s3_pkt.c on line 586. Researching this error, I found a discussion among some of your developers, who experienced the same issue during their own compilation attempts. They created a bug report at http://rt.openssl.org/Ticket/Display.html?id=3376. The ticket was marked as resolved on 5.6.2014; however, I again downloaded the source from openssl.org last night and examined ssl/s3_pkt.c. I observed that the limits.h include statement is still omitted, thus producing the compilation error. I edited s3_pkt.c by adding #include , and successfully compiled OpenSSL 1.0.0m. ### Bug Report Information OS: Oracle Solaris 10 Sparc OpenSSL version: 1.0.0m Compilation Error: s3_pkt.c: In function `ssl3_write_bytes': s3_pkt.c:586: error: `INT_MAX' undeclared (first use in this function) s3_pkt.c:586: error: (Each undeclared identifier is reported only once s3_pkt.c:586: error: for each function it appears in.) make[1]: *** [s3_pkt.o] Error 1 make[1]: Leaving directory `/opt/temp/openssl-1.0.0m/ssl' make: *** [build_ssl] Error 1 Regards, J. Jeff Clemmer IT Specialist Phone: 434-980-7525 Email: john.j.clemmer4@mail.mil __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #3413] OpenSSL Bug Report Submission - related to #3376
On Sat, Jun 28, 2014 at 05:21:40PM +0200, Clemmer, John J CIV via RT wrote: > OpenSSL Development Team, > > My attempts to compile OpenSSL v.1.0.0m on the day of its release as well as > last night both resulted in the same error, whereby INT_MAX is used before it > is declared in ssl/s3_pkt.c on line 586. The problem is solved. There just wasn't a released with the fix yet. Kurt __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org