Comment #7 on issue 20669 by [email protected]: Implement extension  
packing on linux
http://code.google.com/p/chromium/issues/detail?id=20669

The following revision refers to this bug:
     http://src.chromium.org/viewvc/chrome?view=rev&revision=27033

------------------------------------------------------------------------
r27033 | [email protected] | 2009-09-23 18:21:12 -0700 (Wed, 23 Sep  
2009) | 9 lines
Changed paths:
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/base/base.gyp?r1=27033&r2=27032
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/base/crypto/rsa_private_key.h?r1=27033&r2=27032
    A  
http://src.chromium.org/viewvc/chrome/trunk/src/base/crypto/rsa_private_key_nss.cc
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/base/crypto/signature_creator.h?r1=27033&r2=27032
    A  
http://src.chromium.org/viewvc/chrome/trunk/src/base/crypto/signature_creator_nss.cc
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/base/crypto/signature_creator_win.cc?r1=27033&r2=27032
    M  
http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/memcheck/suppressions.txt?r1=27033&r2=27032

Reland: Linux (nss) implementations of RSAPrivateKey and SignatureCreator.

This relands: http://codereview.chromium.org/208032.

Additionally, it fixes a memleak unconvered by valgrind, and adds a  
valgrind supression for a memleak discovered in the nss library.  
https://bugzilla.mozilla.org/show_bug.cgi?id=518443

BUG=20669

Review URL: http://codereview.chromium.org/218010
------------------------------------------------------------------------


--
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to