EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Password longer than 31 characters

Also by EldoS: RawDisk
Access locked and protected files in Windows, read and write disks and partitions and more.
#12486
Posted: 02/18/2010 15:00:07
by Mario Frechette (Standard support level)
Joined: 11/20/2009
Posts: 7

Why there is a disparity between Eldos and Microsoft when a certificate is saved with a password that is having a length of more than 31 characters?

If a certificate that is saved by Eldos (X509CertificateEx.SaveToStreamPFX) with a password that having a length longer than 31 characters, Microsoft can't read it (X509Certificate2.New).

Inversely, if a certificate that is saved by Microsoft (X509Certificate2.Export) with a password that having a length longer than 31 characters, Elos can't read it (X509CertificateEx.LoadFromBufferPFX).
#12492
Posted: 02/19/2010 00:31:43
by Ken Ivanov (EldoS Corp.)

Thank you for reporting the issue. Will be checked.
#12493
Posted: 02/19/2010 00:33:53
by Eugene Mayevski (EldoS Corp.)

EldoS doesn't read certificates. It's a company.


Sincerely yours
Eugene Mayevski
#12496
Posted: 02/19/2010 00:59:14
by Ken Ivanov (EldoS Corp.)

It is actually nothing to check here. I recalled that Microsoft CryptoAPI has a limitation for the length of PFX passwords of 32 characters including trailing zero character. I haven't found an exact confirmation link (stating this for X509Certificate2 class), but found the following ones instead:
http://msdn.microsoft.com/en-us/libra...85%29.aspx
http://msdn.microsoft.com/en-us/libra...85%29.aspx

As both CAPICOM and .NET use the same CryptoAPI internally, it is natural to have the same limitation for .NET components.

Reply

Statistics

Topic viewed 1750 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!