Cerr:
> Hi There,
>
> I would like to open a session to an open ssl http server on port 443
> without any manual keyboard entry.
>
> I've tried the following:
> cat ./logininfo | openssl s_client -connect 192.168.167.166:443
> where logininfo contains
> GET / HTTP/1.1
> host: hostname.com
> Aut
On Wed, Feb 17, 2010 at 10:35 PM, cerr wrote:
>
>
> Scott Gifford wrote:
> >
> > On Wed, Feb 17, 2010 at 6:38 PM, cerr wrote:
> >
> >>
> >> Hi There,
> >>
> >> I would like to open a session to an open ssl http server on port 443
> >> without any manual keyboard entry.
> >
> > [ ... ]
> >
> > Pr
Scott Gifford wrote:
>
> On Wed, Feb 17, 2010 at 6:38 PM, cerr wrote:
>
>>
>> Hi There,
>>
>> I would like to open a session to an open ssl http server on port 443
>> without any manual keyboard entry.
>
> [ ... ]
>
> Probably a copy of curl or wget compiled with SSL support will do what you
hello,
i am running our own server on CentOS 5 using openssl 0.9.8e. i have
not had any problems with it when connecting to with all firefox on
multiple platforms and IE. but when i try with safari on mac os x, the
server is seemingly randomly giving me this error from SSL_accept:
20189:error:1
On Wed, Feb 17, 2010 at 6:38 PM, cerr wrote:
>
> Hi There,
>
> I would like to open a session to an open ssl http server on port 443
> without any manual keyboard entry.
[ ... ]
Probably a copy of curl or wget compiled with SSL support will do what you
want without too much trouble. On Debian
On Wed February 17 2010, cerr wrote:
>
> Hi There,
>
> I would like to open a session to an open ssl http server on port 443
> without any manual keyboard entry.
>
> I've tried the following:
> cat ./logininfo | openssl s_client -connect 192.168.167.166:443
> where logininfo contains
> GET / HTT
Hi There,
I would like to open a session to an open ssl http server on port 443
without any manual keyboard entry.
I've tried the following:
cat ./logininfo | openssl s_client -connect 192.168.167.166:443
where logininfo contains
GET / HTTP/1.1
host: hostname.com
Authorization: BASIC YWRtaW46YWR
> My question is, does the token's PKI engine just do step 5, or does it do
the crypto parts of both 4 and 5? any additional parts of this sequence .?
I worked with a similar context recently, using a custom hardware pkcs11
token & a custom engine, the only operation handled by the hardware token
I am not sure if you are using the following command. It parses the
certs & keys.
#openssl pkcs12 -info -nodes -in
Thanks
-Ashok
On Wed, Feb 17, 2010 at 9:33 AM, Nicolas Pelloux-Prayer
wrote:
> I'm trying to extract the cert/private key pair from a pkcs#12 file using
> the PKCS12_parse method.
I'm trying to extract the cert/private key pair from a pkcs#12 file using
the PKCS12_parse method. It works fine for most p12 I used before, then I
ran into a strange p12 which doesnt work (returned cert & pkey are both
NULL).
Its structure is :
**
10 matches
Mail list logo