Re: pkcs12 export password incorrect

2006-12-09 Thread Victor Duchovni
On Sat, Dec 09, 2006 at 09:35:18AM -0500, Chris Covington wrote: > Would be it possible for you to duplicate Windows' behavior in the > case of exactly 32 character passwords (32 being the limit)? So that > they can be imported into Windows' stores? That would be very helpful > in our case, wher

Re: pkcs12 export password incorrect

2006-12-09 Thread Chris Covington
On 12/8/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote: On Fri, Dec 08, 2006, Chris Covington wrote: > On 12/8/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote: > >> Windows allows up to 32 character passwords. It seems when openssl > >> exports a 32 character password pkcs12 file, Windows do

Re: pkcs12 export password incorrect

2006-12-08 Thread Dr. Stephen Henson
On Fri, Dec 08, 2006, Chris Covington wrote: > On 12/8/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote: > >> Windows allows up to 32 character passwords. It seems when openssl > >> exports a 32 character password pkcs12 file, Windows does not > >> recognize the results, which is unfortunate in m

Re: pkcs12 export password incorrect

2006-12-08 Thread Chris Covington
On 12/8/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote: > Windows allows up to 32 character passwords. It seems when openssl > exports a 32 character password pkcs12 file, Windows does not > recognize the results, which is unfortunate in my case because I > specifically need a 32 character pas

Re: pkcs12 export password incorrect

2006-12-08 Thread Dr. Stephen Henson
On Fri, Dec 08, 2006, Chris Covington wrote: > On 12/8/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote: > >On Fri, Dec 08, 2006, Chris Covington wrote: > > > >> pps - if I import the openssl pkcs12 bundle with a 31 character > >> password, then export it using the Windows GUI with a 32 character

Re: pkcs12 export password incorrect

2006-12-08 Thread Chris Covington
On 12/8/06, Dr. Stephen Henson <[EMAIL PROTECTED]> wrote: On Fri, Dec 08, 2006, Chris Covington wrote: > pps - if I import the openssl pkcs12 bundle with a 31 character > password, then export it using the Windows GUI with a 32 character > password, that 32 character password works as well. How

Re: pkcs12 export password incorrect

2006-12-08 Thread Dr. Stephen Henson
On Fri, Dec 08, 2006, Chris Covington wrote: > pps - if I import the openssl pkcs12 bundle with a 31 character > password, then export it using the Windows GUI with a 32 character > password, that 32 character password works as well. How can I get > openssl to sign these 32 character export passw

Re: pkcs12 export password incorrect

2006-12-08 Thread Chris Covington
pps - if I import the openssl pkcs12 bundle with a 31 character password, then export it using the Windows GUI with a 32 character password, that 32 character password works as well. How can I get openssl to sign these 32 character export passworded pkcs12 bundles in a Windows-compatible way? I'

Re: pkcs12 export password incorrect

2006-12-08 Thread Chris Covington
ps - the openssl Export password can be up to 31 characters. Once I hit that 32nd character, Windows doesn't recognize the password. However, if I use the Active Directory CA, I can correctly import the 32 character password? Chris ___

pkcs12 export password incorrect

2006-12-08 Thread Chris Covington
Hello all, I've created pkcs12 bundles for Windows clients: openssl pkcs12 -export -out w09prntec09.p12 -in w09prntec09.cert.pem -inkey w09prntec09.key.pem -passout pass:AE5B7FDA7ED10248B257F3F1B23A3AFE When I try to import the pkcs12 bundle file into Windows, Windows (XP, 2000, 2003) tells me