-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I found the cause of my issue: When creating a new intermediate ca, I did
not purge the old directory, thus starting with an serial>01 and issued
certificates, revocation list which does not match the new private key.
Still my wish remains:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm trying to sign a csr by running
`CA=signing-ca openssl ca -verbose -config /etc/simple-pki/ca-ssl.conf -name
signing_ca -in /tmp/tmp.Qz3EoKa0S4/fileserver-lo.ddns.eckner.net.csr -out
/tmp/tmp.Qz3EoKa0S4/fileserver-lo.ddns.eckner.net.crt -
ote:
>> Hi there,
>> I'm facing 'Unkown CA' error during ssl handshake messages between
>> client(a network device) and server (pound).
>> sorry am not much familiar with openssl library usage but setting up
>> the pound reverse proxy which use openssl
On 4/18/2012 8:47 PM, Appaji Yelamarthi wrote:
Hi there,
I'm facing 'Unkown CA' error during ssl handshake messages between
client(a network device) and server (pound).
sorry am not much familiar with openssl library usage but setting up
the pound reverse proxy which use openssl
Hi there,
I'm facing 'Unkown CA' error during ssl handshake messages between
client(a network device) and server (pound).
sorry am not much familiar with openssl library usage but setting up
the pound reverse proxy which use openssl 0.9.8 on redhat linux.
Done a lot of googli
I am trying to run the following command:
[root@localhost certs]# openssl s_client -connect localhost:7043 -cert
/opt/openssl-1.0.0a/ssl/
certwork_client/client.crt -key
/opt/openssl-1.0.0a/ssl/certwork_client/client.key -CAfile
/opt/openssl-1.0.0a/ssl/certwork/ca.crt -showcerts -state -verify 2
v
server and opens a socket and calls
>> SSL_Connect(). Server sends his certificate. Client notices that
>> server has a older CA and returns UNKNOWN CA error.
>>
>> At this point can we reuse the socket by cleaning up the old SSL
>> connection and
g to connect to server and opens a socket and calls
> SSL_Connect(). Server sends his certificate. Client notices that
> server has a older CA and returns UNKNOWN CA error.
>
> At this point can we reuse the socket by cleaning up the ol
to server and opens a socket and calls
SSL_Connect(). Server sends his certificate. Client notices that
server has a older CA and returns UNKNOWN CA error.
At this point can we reuse the socket by cleaning up the old SSL
connection and recreating a new one?
--Satish
Hello Dr.Stephen,
The cmd switches I am using are
OpenSSL> s_client -connect :443 -state
-cert leafcert.pem -key
privkey.pem -CAfile nyisobag.pem
Loading 'screen' into random state - done
Enter PEM pass phrase:
840:error:0906D066:PEM routines:PEM_read_bio:bad end
line:.\crypto\pem\pem_lib.c
:736
On Tue, Aug 03, 2004, nathv wrote:
> Hello All,
>
> I am trying to access a server using s_client and I am
> passing the leaf and self signed CA of the server
> through -CAfile switch, but I am still getting the
> error below, any ideas?.
>
> .
> SSL_connect:SSLv3 write certificate verify A
On Wed, Apr 24, 2002 at 04:18:49PM -0300, Jay States wrote:
> I am use learning and testing CA's. I have tried to create a
> self-signed CA certificate using the following:
>
> openssl req -new -x509 -days 365 -key sample.key -out sample.crt
>
> and this is the error message that I get. I re-b
I am use learning and testing CA's. I have tried to create a
self-signed CA certificate using the following:
openssl req -new -x509 -days 365 -key sample.key -out sample.crt
and this is the error message that I get. I re-built openssl and
openssh, but I still get this error. What am I doing
13 matches
Mail list logo
