Fred3rik

Supports defining following elements in pkcs signing and encryption: * SubjectKeyIdentifier as SignerIdentifier (alternative choice for IssuerAndSerialNumber) * SubjectKeyIdentifier as RecipientIdentifier (alternative choice for IssuerAndSerialNumber) * Support for RSASSA-PSS as...

In cases where the recipient is not yet known or it is a group of recipients that may share a secret, encryption should be done with a secret key. this...

Add support for SubjectKeyIdentifier in CMS message (PKCS#7)

1

A SignerIdentifier or RecipientIdentifier references the public key of the signer or recipient. Currently this requires an x509 certificate of which the issuer and serialnumber are taken. The spec supports...

Add support for RSASSA-PSS as scheme to sign CMS message (PKCS#7)

1

forge supports signing with RSASSA-PSS scheme but currently not for CMS messages (PKCS#7). As this scheme is more secure then RSASSA-PKCS1-V1_5, it should be possible to choose that one as...

External Token Exchange through UserInfo doesn't work with signed response

5

### Before reporting an issue - [X] I have searched existing issues - [X] I have reproduced the issue with the latest release ### Area token-exchange ### Describe the bug...

This change makes browserify-rsa run in a browser, clientside, which is mainly the purpose of having a browserify module. browserify-rsa depends on Buffer, which is part of Node js API,...