(Forwarded to openssl-users)
The subjectName of file4.pem matches the issuerName of file3.pem, the
signature block in file3.pem, when verified with the public key of
file4.pem, gives a correct signature for the tbsCertificate of file3.pem.
But Openssl also (incorrectly, IMO) checks that
Ok, whith few modifications to fipsld++ i can now link to libcrypto.so
and libcrypto.a and applications are working correctly, but mine problem
still persists because if i would like to dlopen my shared library
compiled with static libcrypto.a and i'll try to run fips mode from that
library i get
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
Of Salz, Rich
Sent: Friday, April 03, 2015 15:55
To: openssl-users@openssl.org
Subject: Re: [openssl-users] HTTP / HTTPS on same port
It is a hack.
That's debatable. What's so sacred about separating traffic by port?
I am thinking about removing compression and would like to know what the
community thinks.
At a minimum, I am going to remove the ability to add compression at run-time.
This was never really documented. Moving forward, if someone wants to add a new
compression scheme they will need to modify
It is a hack. Most people do it the other way and look for a G or P as the
first letter.
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hello Mike, Don and Matt,
At the point I am at this list of servers in my script I would really need
someone with more experience to see if I even have the right scripting.
#!/usr/bin/perl
use strict;
use Expect;
my $timeout = 60;
my @servers = qw(
remotehost03
remotehost04
On 03/04/15 20:48, Joris Van Remoortere wrote:
Hello,
I would like to ask your opinion and advice on accepting HTTP / HTTPS
connections on the same port.
I currently have a prototype that peeks at the first byte after
accepting a new connection, and dispatches to the appropriate
Hello,
I would like to ask your opinion and advice on accepting HTTP / HTTPS
connections on the same port.
I currently have a prototype that peeks at the first byte after accepting a
new connection, and dispatches to the appropriate routines based on whether
the first byte is 0x16 or not. This
Hi,
I suggested one such implementation in mongoose opensource web server
You can check it in .
https://groups.google.com/forum/#!msg/mongoose-users/IAzYHF0do-I/INc_VmLAe6gJ
This is the function I added
let me know if it is useful.
static int CheckSSL(int nSocket)
{
/* taken from s23_svr.c
On 04/04/2015 07:18, Jakob Bohm wrote:
On 04/04/2015 04:07, Mabry Tyson wrote:
I happened to notice what seems to be an output glitch in the textual
output of a certificate.
I received a copy of the QuoVadis Root CA 2 certificate as a file.
When I examined the certificate via
openssl
JR == Joris Van Remoortere jo...@mesosphere.io writes:
JR I would like to ask your opinion and advice on accepting HTTP / HTTPS
JR connections on the same port.
IPP support both w/ and w/o tls on port 631.
Cups handles it like this:
http://www.pwg.org/archives/ipp/2014/017906.html
-JimC
--
I happened to notice what seems to be an output glitch in the textual
output of a certificate.
I received a copy of the QuoVadis Root CA 2 certificate as a file. When
I examined the certificate via
openssl x509 -text -in /tmp/QV.cer(using OpenSSL 1.0.1 14 Mar
2012 as installed in
On 04/04/2015 04:07, Mabry Tyson wrote:
I happened to notice what seems to be an output glitch in the textual
output of a certificate.
I received a copy of the QuoVadis Root CA 2 certificate as a file.
When I examined the certificate via
openssl x509 -text -in /tmp/QV.cer(using
(top posting like the rest of the thread)
What makes you think it is incorrect to check the Key
Identifier (where present) before checking a signature
against a key?
What other reasonable purpose could the Key Identifier
fields serve?
On 03/04/2015 10:56, Erwann Abalea wrote:
(Forwarded to
On 03/04/2015 22:12, Michael Wojcik wrote:
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
Of Salz, Rich
Sent: Friday, April 03, 2015 15:55
To: openssl-users@openssl.org
Subject: Re: [openssl-users] HTTP / HTTPS on same port
It is a hack.
That's debatable. What's so
Ok i have finally managed to find what is the problem. The generated
value of digest under linux had bad value. Now i have to correct incore
file for QNX platform. Wish me luck or if anybody can help me with this
i would be pleased. :)
Dnia 2015-04-03, pią o godzinie 11:16 +0200, Piotr Łobacz
16 matches
Mail list logo
