-
-
Replying to @WatsonLadd
@WatsonLadd@kaepora@sleevi_ last I looked WebCrypto only non-normatively included RSASSA PkCS#1v1.5 *signatures* which are fine2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@WatsonLadd@kaepora RSAES-PKCS1-v1_5. Along with RSA-OAEP, but no RSA-KEM2 replies 0 retweets 0 likes -
Replying to @sleevi_
@sleevi_@bascule@kaepora Yeah, that's the broken one. http://link.springer.com/chapter/10.1007%2FBFb0055716?LI=true#page-1 …2 replies 0 retweets 0 likes -
Replying to @WatsonLadd
@WatsonLadd@sleevi_@kaepora I am aware of the attacks. It wasn’t in older drafts of the WebCrypto API though1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@WatsonLadd@kaepora Um, it's been in since 2012 - http://www.w3.org/TR/2012/WD-WebCryptoAPI-20120913/ …2 replies 0 retweets 0 likes -
Replying to @sleevi_
@sleevi_@WatsonLadd@kaepora I swear it was only RSASSA at one point. Perhaps@matthew_d_green remembers?2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@sleevi_@WatsonLadd@kaepora I think RSASSA was in the Recommended section, and RSAES was just supported...1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.