RE: how to enable the internal client crypto on WPA_supplicant

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Oh, 

One final question, can you (please) suggest what format the internal crypto support ?
Then I will see if I can convert it / or generate the suitable private key to this purpose 

Once again thank you for your time !


-----Original Message-----
From: Jouni Malinen [mailto:j@xxxxx] 
Sent: 4. december 2015 10:41
To: Achuthan Paramanathan <acp@xxxxxx>
Cc: Hostap@xxxxxxxxxxxxxxxxxxx
Subject: Re: how to enable the internal client crypto on WPA_supplicant

On Fri, Dec 04, 2015 at 09:31:37AM +0000, Achuthan Paramanathan wrote:
> I am getting an error when I read in my private key (the same private 
> key I use while not have enabled the internal crypto ie. using 
> openSSL)

> My guess is that the format is wrong (not that difficult to see that :) )...but the question is what format if not the format is the same as for openssl ?

> PKCS #8: Expected INTEGER - found class 0 tag 0x10; assume PKCS #8 not 
> used PKCS #5: encryption algorithm 1.2.840.113549.1.5.13 PKCS #5: 
> unsupported encryption algorithm 1.2.840.113549.1.5.13 PKCS #5: 
> Unsupported parameters

The format itself is likely fine, but the internal crypto code does not yet support PBES2 which explains why this private key cannot be used.

-- 
Jouni Malinen                                            PGP id EFC895FA

_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux