Comment #1 on issue 14877 by [email protected]: RSAPrivateKey decoding
ocassionally fails
http://code.google.com/p/chromium/issues/detail?id=14877
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=18909
------------------------------------------------------------------------
r18909 | [email protected] | 2009-06-22 10:17:26 -0700 (Mon, 22 Jun 2009) |
12 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/crypto/rsa_private_key_unittest.cc?r1=18909&r2=18908
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/crypto/rsa_private_key_win.cc?r1=18909&r2=18908
Fix decoding bug in RSAPrivateKey.
We were dropping the most significant byte from the input when
decoding PrivateKeyInfo, whether or not it was part of the
original data. This shouldn't matter, except that we need to
get back the original byte lengths so that we can give them to
CryptoAPI.
BUG=14877
TEST=Stress tested the functions by creating 1000 random private keys,
exporting them, then re-importing. Also tried stressing the edge cases in
particular around extra trailing null bytes.
Review URL: http://codereview.chromium.org/141036
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
