[openssl-users] FIPS: Error compiling 1.0.1e: 'T' vs. 't'
Hello, There is a problem with compiling the openssl-1.0.1e.tar.gz sources against the FIPS 2.0 canister. On my machine the following is declared global: 000dd3c0 T private_AES_set_decrypt_key 000dd0f0 T private_AES_set_encrypt_key On another machine, they are declared local and the apps build fails: 000dd3c0 t private_AES_set_decrypt_key 000dd0f0 t private_AES_set_encrypt_key What is the mecanism that determines which is global and which is local and what does it depend on to make its decision ? Regards. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] FIPS: Error compiling 1.0.1e: 'T' vs. 't'
Hello, There is a problem with compiling the openssl-1.0.1e.tar.gz sources against the FIPS 2.0 canister. On my machine the following is declared global: 000dd3c0 T private_AES_set_decrypt_key 000dd0f0 T private_AES_set_encrypt_key On another machine, they are declared local and the apps build fails: 000dd3c0 t private_AES_set_decrypt_key 000dd0f0 t private_AES_set_encrypt_key What is the mechanism that determines which is global and which is local and what does it depend on to make its decision ? Regards. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] SSL_ERROR_WANT_READ but nothing to read
On 17/03/15 00:51, Narada Hess wrote: HI, I have a client application using a single read-write socket in non-blocking mode. In C, on Linux, using openssl 1.0.1e. After the connection is established and all the initial handshaking is done, the client issues SSL_read(), then enters a loop of: - Interpret results (such as break upon socket close) - select() on the socket - SSL_read() again . . . until the expected number of bytes have been read. The first SSL_read() returns SSL_ERROR_WANT_READ and loops to attempt to retry the operation. But select() indicates that the socket is not readable, so we block forever and the server times out (the server had written a record which the client never reads). I experimented by skipping the select() and just sleeping a little, but in that case, infinite retries of SSL_read() did not help. Another experiment was to try writing some arbitrary data. That _/DID/_ seem to help and moved the protocol forwards a bit. But I shouldn’t have to do that – we have nothing to write until we have received the full read record. In case it matters, the server on the other end is an OpenDaylight controller. Its logs indicate successful handshake, appropriate cipher suite, etc. And my test client-server application using this logic works just fine. Also, no SSL_writes() are happening during this, or any other operation that would change the SSL* object state, AFAIK. I’ve tried Wireshark on this, but I have not been able to glean too much from it, as everything is encrypted and also it seems to be showing transport sized packets of 15xx bytes instead of application sized records – could that be pointing at the problem? I did not set the read_ahead option. Any ideas? I have spent hours reading the SSL documentation (such as SSL_get_error) and many, many posts and answers, plus several SSL books. It seems that I am doing the right thing here. So why is select() blocking? There is no outstanding write operation, so shouldn’t a retry of SSL_read() clear any handshake/renegotiation stuff? Are you sure the record that the server wrote actually got sent across the network? Have you tried connecting to the server using s_client? Does that succeed? Matt ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Forthcoming OpenSSL releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/03/15 00:32, Sec_Aficionado wrote: Thanks for the heads up. Just to confirm, is this highest severity defect a yet-to-be-disclosed vulnerability, or a fix for an already known one? This is a previously undisclosed vulnerability. Matt -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVCABuAAoJENnE0m0OYESRmtQH/RJMDjBTBfEY/Va6sM49TYlh Zn4BVV9a6PLOtPlGS9J23bonolC63Aqgh7SWrMTl+Vosrlw2ZL8kXFCgT9ROpPYh woX5nzrt1aLMLDf1AahjY2shnsOsp6glCVSH2YnvkUIot4OKhDaXhjxf44er/qFZ Tc3RTtfTOjcamu/2uhpRnegaZM5QGLm9/5Rkb+iPBVFgAGCaDmIR4KqWSl5VxsV/ xhe7PU/KCXUXgWe9Wou5KrvsWKW02kuJvz5CMMSE6BcYPLaNZEbrtkyaOj5VoSBH 2qDSR4nJeMGXH+uChJSDf90q8yRhnp3Uyha0uEabxo2lzQksaDCL3Tz87NfMPkI= =Uygc -END PGP SIGNATURE- ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] FIPS: Problem building 1.0.1e: 'T' vs. 't'
From: Dr. Stephen Henson st...@openssl.org Date: 03/17/15 12:28 What are the two platforms? That is what does: First of all, I'm very, very sorry to have posted duplicates of the question. The web-access email client is, was, a bit on the fuzzy side, stalling and reporting errors. It turns out, at the end of much puzzling and searching, that the difference is in the Debian packaging. The Debian folks have added some per-method version mechanism to be assured that the APIs are still compatible between OpenSSL number versions. That mechanism does not recognize the FIPS renaming of some methods hence tags them as local. We fixed that and it could be that the fix can be given to Debian as it should be transparent to non-FIPS OpenSSL Debian builds. Again, sorry for the multiple posts ! Regards. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] TLS 1.2 message hiding.
Ok, so TLS does not handle this. The current draft of the TLS 1.3 specification includes a field to pad every data record. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] question about resigning a certificate
Hi I have done that and compared the output with diff The only differences are Serial number Signature algo Comment Signature. Alex From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Jakob Bohm Sent: Wednesday, 18 March 2015 6:50 AM To: openssl-users@openssl.org Subject: Re: [openssl-users] question about resigning a certificate On 16/03/2015 02:46, Alex Samad - Yieldbroker wrote: Hi I had a sha1 signed CA and I issued other identity and CA certificates from this CA. With the deprecation of sha1 coming, I resigned my original CA (self signed) as sha512, with the same creation and expiry dates. I believe the only thing changed was the signature and serial number. But when I go to verify older certs that were signed by the original CA (the sha1 signed one), they are no longer valid. I thought if I used the same private and public key I should be okay. I thought the only relevant issue was the issuer field and that the CA keys where the same . Was I wrong. Alex Run openssl x509 -noout -text -in OneOfYourIssuedCerts.pem | more Look at what aspects of your CA are mentioned. For example, does it include the X509v3 Authority Key Identifier extension, and if so, which fields from the CA cert are included? Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] SSL_ERROR_WANT_READ but nothing to read
In case anyone is following this thread, Matt's suggestion led to the solution. It turns out we weren't getting a packet from the remote end and all my angst was for naught. Thanks, Matt, for your help. N -Original Message- From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Matt Caswell Sent: Tuesday, March 17, 2015 4:03 AM To: openssl-users@openssl.org Subject: Re: [openssl-users] SSL_ERROR_WANT_READ but nothing to read On 17/03/15 00:51, Narada Hess wrote: HI, I have a client application using a single read-write socket in non-blocking mode. In C, on Linux, using openssl 1.0.1e. After the connection is established and all the initial handshaking is done, the client issues SSL_read(), then enters a loop of: - Interpret results (such as break upon socket close) - select() on the socket - SSL_read() again . . . until the expected number of bytes have been read. The first SSL_read() returns SSL_ERROR_WANT_READ and loops to attempt to retry the operation. But select() indicates that the socket is not readable, so we block forever and the server times out (the server had written a record which the client never reads). I experimented by skipping the select() and just sleeping a little, but in that case, infinite retries of SSL_read() did not help. Another experiment was to try writing some arbitrary data. That _/DID/_ seem to help and moved the protocol forwards a bit. But I shouldn't have to do that - we have nothing to write until we have received the full read record. In case it matters, the server on the other end is an OpenDaylight controller. Its logs indicate successful handshake, appropriate cipher suite, etc. And my test client-server application using this logic works just fine. Also, no SSL_writes() are happening during this, or any other operation that would change the SSL* object state, AFAIK. I've tried Wireshark on this, but I have not been able to glean too much from it, as everything is encrypted and also it seems to be showing transport sized packets of 15xx bytes instead of application sized records - could that be pointing at the problem? I did not set the read_ahead option. Any ideas? I have spent hours reading the SSL documentation (such as SSL_get_error) and many, many posts and answers, plus several SSL books. It seems that I am doing the right thing here. So why is select() blocking? There is no outstanding write operation, so shouldn't a retry of SSL_read() clear any handshake/renegotiation stuff? Are you sure the record that the server wrote actually got sent across the network? Have you tried connecting to the server using s_client? Does that succeed? Matt ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] question about resigning a certificate
On 16/03/2015 02:46, Alex Samad - Yieldbroker wrote: Hi I had a sha1 signed CA and I issued other identity and CA certificates from this CA. With the deprecation of sha1 coming, I resigned my original CA (self signed) as sha512, with the same creation and expiry dates. I believe the only thing changed was the signature and serial number. But when I go to verify older certs that were signed by the original CA (the sha1 signed one), they are no longer valid. I thought if I used the same private and public key I should be okay. I thought the only relevant issue was the issuer field and that the CA keys where the same . Was I wrong. Alex Run openssl x509 -noout -text -in OneOfYourIssuedCerts.pem| more Look at what aspects of your CA are mentioned. For example, does it include the X509v3 Authority Key Identifier extension, and if so, which fields from the CA cert are included? Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Reg : SCEP using OPENSSL
If it fits your needs, you may want to look into using EST (RFC 7030) instead of SCEP. EST is the replacement for SCEP. The SCEP draft was never ratified. The libest open source project implements RFC 7030 and uses OpenSSL. It's available at https://github.com/cisco/libest. On 03/17/2015 12:01 AM, Sindhu S. (sins) wrote: Hi all, I need guidance in understanding as to how SCEP server can be used integrated with OpenSSL. My understanding is that SCEP can be used to enroll devices then it communicates to Certificate Authority that generate certificates. Can some one point me in right direction ? Basically i am trying to achieve following: Using SCEP to enroll devices then generate Certificates usingCA. Any reference to opensource SCEP will be helpful… I’m also exploring few opensource SCEP implementation, like openscep, sscep, autosscep.. etc…. https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif Thanks, Sindhu ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] What is the format for a parameter file (-paramfile option)?
I am attempting to generate keys using genpkey, with the RSA options specified in a parameter file: openssl genpkey -paramfile keygen.params -out ftest.key -outform PEM However, I'm constantly getting the following error: Error reading parameter file keygen.params I can't find any documentation or examples on what format the parameter file should be in. Can someone either provide an example of what the parameter file should look like, or point to me to one online? I'm not having any trouble getting it to work with the parameters specified on the command line, but for various reasons would like to have them in a file. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] What is the format for a parameter file (-paramfile option)?
On Tue, Mar 17, 2015, Michael Stickles wrote: I am attempting to generate keys using genpkey, with the RSA options specified in a parameter file: openssl genpkey -paramfile keygen.params -out ftest.key -outform PEM However, I'm constantly getting the following error: Error reading parameter file keygen.params I can't find any documentation or examples on what format the parameter file should be in. Can someone either provide an example of what the parameter file should look like, or point to me to one online? I'm not having any trouble getting it to work with the parameters specified on the command line, but for various reasons would like to have them in a file. The parameter file is a set of parameters associated with the algorithm and is typically generated using the -genparam command line option. For RSA there is no associated parameter file which is why you get errors. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] FIPS: Problem building 1.0.1e : 'T' vs. 't'
Hello, There is a problem with compiling the openssl-1.0.1e.tar.gz sources against the FIPS 2.0 canister. On my machine the following is declared global: 000dd3c0 T private_AES_set_decrypt_key 000dd0f0 T private_AES_set_encrypt_key On another machine, they are declared local and the apps build fails: 000dd3c0 t private_AES_set_decrypt_key 000dd0f0 t private_AES_set_encrypt_key What is the mecanism that determines which is global and which is local and what does it depend on to make its decision ? Regards. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] FIPS: Problem building 1.0.1e : 'T' vs. 't'
On Tue, Mar 17, 2015, jonetsu wrote: Hello, There is a problem with compiling the openssl-1.0.1e.tar.gz sources against the FIPS 2.0 canister. On my machine the following is declared global: 000dd3c0 T private_AES_set_decrypt_key 000dd0f0 T private_AES_set_encrypt_key On another machine, they are declared local and the apps build fails: 000dd3c0 t private_AES_set_decrypt_key 000dd0f0 t private_AES_set_encrypt_key What is the mecanism that determines which is global and which is local and what does it depend on to make its decision ? What are the two platforms? That is what does: ./config -t output? Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] openssl 1.0.2 shared build's linking is not consistent - bin and libs linked to different libcrypto.so's
I'm trying to build a library self-consistent instance of openssl 1.0.2 on
linux/64.
Setting *FLAGS rpath, although the openssl binary links correctly against its
own {libcrypto,libssl}.so, the libssl.so links against *system*, not its own,
libcrypto.
I've tried a bunch of combinations of *FLAGS. Always the same result. The
current env/result is:
cd ./openssl-1.0.2
export SHARED_LDFLAGS=-L/usr/local/sslTEST/lib64
-Wl,-rpath,/usr/local/sslTEST/lib64 -lssl -lcrypto
export LDFLAGS=${SHARED_LDFLAGS}
export LIBDEPS=${SHARED_LDFLAGS}
./config \
--openssldir=/usr/local/sslTEST \
--libdir=lib64 \
threads shared zlib \
enable-ec_nistp_64_gcc_128 \
no-idea \
no-ssl2 \
no-rc5 \
no-mdc2 \
no-hw \
no-ec2m \
enable-rfc3779
make depend
make
make install
There are no apparent errors in the build output.
The build results in
/usr/local/sslTEST/bin/openssl version
OpenSSL 1.0.2 22 Jan 2015
ldd \
/usr/local/sslTEST/bin/openssl \
/usr/local/sslTEST/lib64/libssl.so.1.0.0 \
/usr/local/sslTEST/lib64/libcrypto.so.1.0.0
/usr/local/sslTEST/bin/openssl:
linux-vdso.so.1 (0x7ffefffd7000)
libssl.so.1.0.0 =
/usr/local/sslTEST/lib64/libssl.so.1.0.0 (0x7f93cbe0e000)
!! libcrypto.so.1.0.0 =
/usr/local/sslTEST/lib64/libcrypto.so.1.0.0 (0x7f93cb9ce000)
libdl.so.2 = /lib64/libdl.so.2 (0x7f93cb77f000)
libz.so.1 = /lib64/libz.so.1 (0x7f93cb569000)
libc.so.6 = /lib64/libc.so.6 (0x7f93cb1c1000)
/lib64/ld-linux-x86-64.so.2 (0x7f93cc07a000)
/usr/local/sslTEST/lib64/libssl.so.1.0.0:
linux-vdso.so.1 (0x7ffd01636000)
!! libcrypto.so.1.0.0 = /lib64/libcrypto.so.1.0.0
(0x7ff4abf33000)
libdl.so.2 = /lib64/libdl.so.2 (0x7ff4abd2f000)
libz.so.1 = /lib64/libz.so.1 (0x7ff4abb18000)
libc.so.6 = /lib64/libc.so.6 (0x7ff4ab771000)
/lib64/ld-linux-x86-64.so.2 (0x7ff4ac60d000)
/usr/local/sslTEST/lib64/libcrypto.so.1.0.0:
linux-vdso.so.1 (0x7ffe1f55d000)
libdl.so.2 = /lib64/libdl.so.2 (0x7f9a10f46000)
libz.so.1 = /lib64/libz.so.1 (0x7f9a10d3)
libc.so.6 = /lib64/libc.so.6 (0x7f9a10988000)
/lib64/ld-linux-x86-64.so.2 (0x7f9a115d5000)
where you can see the different libcrypto's are linked.
Wht specific combination and settings of FLAGS are required to ensure that the
bins libs are all self-consistently linked/rpath'd only against this build's
libs?
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] FIPS: Error compiling 1.0.1e: 'T' vs. 't'
Hello, There is a problem with compiling the openssl-1.0.1e.tar.gz sources against the FIPS 2.0 canister. On my machine the following is declared global: 000dd3c0 T private_AES_set_decrypt_key 000dd0f0 T private_AES_set_encrypt_key On another machine, they are declared local and the apps build fails: 000dd3c0 t private_AES_set_decrypt_key 000dd0f0 t private_AES_set_encrypt_key What is the mecanism that determines which is global and which is local and what does it depend on to make its decision ? Regards. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] TLS 1.2 message hiding.
On 03/13/15 20:56, Salz, Rich wrote: I'm using TLS 1.2 with compression and was wondering if OpenSSL implements ways to hide the exact length of the message (may be using RFC 6066). No. What in 6066 were you thinking of trying to use? ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users Ok, so TLS does not handle this. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
