Add RSA-OAEP support from upstream NSS bugs 1009794 and 1009785

Add RSA-OAEP support from upstream NSS bugs 1009794 and 1009785

BUG=372917
R=wtc

[Ryan Sleevi, 2014-05-20 19:02:25]

wtc: PTAL. Just the two upstream patches from me (as checked in) and your
const-correctness fix.

[wtc, 2014-05-20 19:25:57]

Patch set 1 LGTM.

https://codereview.chromium.org/295043002/diff/1/nss/lib/pk11wrap/pk11obj.c
File nss/lib/pk11wrap/pk11obj.c (right):

https://codereview.chromium.org/295043002/diff/1/nss/lib/pk11wrap/pk11obj.c#n...
nss/lib/pk11wrap/pk11obj.c:1067: if (!key || key->keyType != rsaKey) {

It seems that we lost the key type checks in the new PK11_PrivDecrypt and
PK11_PubEncrypt functions. Maybe they're not that useful. To check the key types
here, we'll need to use a switch statement to handle the commonly used
mechanisms.

[Ryan Sleevi, 2014-05-20 21:19:14]

https://codereview.chromium.org/295043002/diff/1/nss/lib/pk11wrap/pk11obj.c
File nss/lib/pk11wrap/pk11obj.c (right):

https://codereview.chromium.org/295043002/diff/1/nss/lib/pk11wrap/pk11obj.c#n...
nss/lib/pk11wrap/pk11obj.c:1067: if (!key || key->keyType != rsaKey) {
On 2014/05/20 19:25:57, wtc wrote:
> 
> It seems that we lost the key type checks in the new PK11_PrivDecrypt and
> PK11_PubEncrypt functions. Maybe they're not that useful. To check the key
types
> here, we'll need to use a switch statement to handle the commonly used
> mechanisms.

This was intentional.

I wanted PK11_PubEncrypt and PK11_PrivDecrypt to work with any asymmetric
algorithms (and their underlying mechanisms), rather than 'just' RSA keys. That
is, they're the 'escape hatch' function for when we don't have generic pk11wrap
utilities.

[Ryan Sleevi, 2014-05-20 21:38:41]

The CQ bit was checked by rsleevi@chromium.org

[commit-bot: I haz the power, 2014-05-20 21:39:09]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rsleevi@chromium.org/295043002/1

[commit-bot: I haz the power, 2014-05-20 21:39:36]

Change committed as 271760