Hello Openssl users,
I have a basic query that
Lets say my SSL client is capable of versions SSL3.0 and SSL3.1.
And my SSL server is capable of versions TLS1.0, TLS1.1 and TLS1.2
Now SSL client has sent a client hello with version SSL3.0. Since, SSL
server doesn't have this version present, it
On Wed, Nov 05, 2014, neil carter wrote:
I just ran the commands again, adding the no-ipv6 to the 'perl
Configure' line and received the exact same errors.
OpenSSL tries to autodetect IPv6 support at compile time. Sometimes due to
broken or incomplete headers it gets this wrong. You can
On 05.11.2014 17:00, Viktor Dukhovni wrote:
On Wed, Nov 05, 2014 at 12:18:05PM +, Philip Bellino wrote:
Jeffrey,
May I ask why you included no-ssl2 as an option to config?
Is only adding no-ssl3 not sufficient enough to fully disable SSLv3?
No. If you leave SSLv2 enabled, and disable
On 06.11.2014 10:02, Rajeswari K wrote:
Hello Openssl users,
I have a basic query that
Lets say my SSL client is capable of versions SSL3.0 and SSL3.1.
And my SSL server is capable of versions TLS1.0, TLS1.1 and TLS1.2
Now SSL client has sent a client hello with version SSL3.0. Since, SSL
That worked!! Thank you!!
So, next is to remove/disable SSL2 and SSL3 from the build, my original
intent.
If I simply add the no-ssl2 and no-ssl3 options to the 'perl Configure'
line, it returns this:
link /nologo /subsystem:console /opt:ref /debug /dll
/out:out32dll\libeay32.dll
On Thu, Nov 06, 2014 at 03:31:10PM +0100, Richard K?nning wrote:
Well, the ClientHello message only allows to advertise the highest protocol
version the client speaks, it is expected that the client speaks also all
lower versions.
The client uses the lowest supported version at the *record
On 06.11.2014 16:35, Viktor Dukhovni wrote:
On Thu, Nov 06, 2014 at 03:31:10PM +0100, Richard K?nning wrote:
Well, the ClientHello message only allows to advertise the highest protocol
version the client speaks, it is expected that the client speaks also all
lower versions.
The client uses
Hello,
i found that the file command detects S/MIME attachment (smime.p7s)
within a signed email as an application/octet-stream insted of
application/pkcs7. Author of the file tool tells that it's impossible to
detect application/pkcs7. Does anybody knows why?
Thank you
Jan
smime.p7s
On Thu, Nov 06, 2014, neil carter wrote:
That worked!! Thank you!!
So, next is to remove/disable SSL2 and SSL3 from the build, my
original intent.
If I simply add the no-ssl2 and no-ssl3 options to the 'perl
Configure' line, it returns this:
There are a few problems with that in
This is my first attempt ever at magic(5) voodoo:
0 byte 0x30
0x01 byte 0x80
0x02 string \x06\x09\x2a\x86\x48\x86\xf7\x0d\x01\x07\x02 Indefinite
length pkcs7-signedData
!:mime application/pkcs7
0x02 string \x06\x09\x2a\x86\x48\x86\xf7\x0d\x01\x07\x03 Indefinite
length pkcs7-envelopedData
Ok, so I downloaded and attempted the same build process on the
openssl-1.0.1-stable-SNAP-20141106.tar.gz and get the exact same errors.
The process:
1.perl Configure VC-WIN32 --prefix=c:\openssl
-DOPENSSL_USE_IPV6=0 -DOPENSSL_NO_SSL2 -DOPENSSL_NO_SSL3
2.ms\do_nasm.bat
3
On Thu, Nov 06, 2014, neil carter wrote:
Ok, so I downloaded and attempted the same build process on the
openssl-1.0.1-stable-SNAP-20141106.tar.gz and get the exact same
errors.
For that you should use no-ssl2 no-ssl3. Some of the build scripts need to
pick up those options.
Steve.
--
Dr
-20141106.tar.gz and get the exact same
errors.
For that you should use no-ssl2 no-ssl3. Some of the build scripts need to
pick up those options.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
On 05/11/2014 20:55, neil carter wrote:
Okay, so what magic script is this? Is it available in MS VS 6.0?
Sorry, not a developer so part of what everyone is saying is beyond me.
I ran the VCVARS32.bat script. Previously that's all I've had to do to
prepare the environment for installing
14 matches
Mail list logo
