Hi
Unfortunately this didn't change anything.
Actually I was already using a PEM-format version of the certificate.
(Same URL as the certificate you linked, but ".cer")
The output is still the same, although now with only -d option
[http://pastebin.com/DPrnguQU]. The SSL error is still the only obvious
error I can find in there. Early on there's a lot of stuff with wpa
authentication failure, but later on it manages to associate with the
Access Point, so that shouldn't be a problem in the end.
So, anyone have any new ideas?
-Aapo Alasuutari
On 06/10/10 14:24, Martin Kaiser wrote:
Hi Aapo,
Thus wrote Aapo Alasuutari (aapo.alasuut...@tut.fi):
Basically it seems like SSL doesn't know what format the certificate is.
Maybe...? I'm not too informed of OpenSSL's behaviour, but judging on
extensive Googling and some similar problems, the solution usually lies
in the format of the certificate.
if your certificate is http://www.ca.tut.fi/ca/tut-ca.crt, then this
file is in DER format. The file contains the raw ASN.1 encoding of the
certificate data.
Try converting the certificate to PEM format
openssl x509 -inform DER -in tut-ca.crt -out tut-ca.pem
and use this file as input to your application.
Best regards,
Martin
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
