WebCrypto use cases doc dives right into a banking example using PKCS#1v1.5 o_O WTF: http://www.w3.org/TR/2013/WD-webcrypto-usecases-20130108/ … /cc @matthew_d_green
-
-
Replying to @bascule
@bascule@matthew_d_green The WebCrypto group has a (TOTALLY INSANE) goal of legacy crypto compat.2 replies 5 retweets 1 like -
Replying to @tqbf
@tqbf@matthew_d_green I was told the goal of WebCrypto was to build a low level API other libs could consume. This example is not that o_O2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@matthew_d_green No, potential for building on top is a “feature” but definitely not “the goal”. The goal is compat.1 reply 0 retweets 0 likes -
Replying to @tqbf
@tqbf@matthew_d_green because backwards compatibility with shitty crypto is so worthwhile1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@matthew_d_green They are doing it so browsers can supplant more native code, not to make crypto better.1 reply 0 retweets 0 likes
Replying to @tqbf
@tqbf @matthew_d_green seems bad
12:14 PM - 9 Jan 2013
0 replies
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.