-
-
Replying to @really_bz1 reply 0 retweets 0 likes
-
Replying to @really_bz
@bz_moz@rmhrisk@sleevi_ Just for info:#PKIjs working in Chrome but does not in Firefox/Aurora/Firefox Nightly.1 reply 0 retweets 0 likes -
Replying to @YuryStrozhevsky
@YuryStrozhevsky@rmhrisk@sleevi_ What makes it not work, exactly?2 replies 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@rmhrisk@sleevi_ Here you can find my example of using WebCrypto http://ow.ly/z24qU . Check if it is working in any Mozilla prod1 reply 0 retweets 0 likes -
Replying to @YuryStrozhevsky
@YuryStrozhevsky@rmhrisk@sleevi_ Looks like having a usage other than "verify" for a public key on that first importKey gives a DataError.2 replies 0 retweets 0 likes -
Replying to @really_bz
@YuryStrozhevsky@rmhrisk@sleevi_ And if I fix that, then the sign() call at the end claims NotSupportedErr, because "sha-1" is not known.1 reply 0 retweets 0 likes -
Replying to @really_bz
@YuryStrozhevsky@rmhrisk@sleevi_ Afaict from spec it should be "SHA-1".1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@YuryStrozhevsky@sleevi_ yes, it seems chrome doesn't care the case. We will update our code to use upper.1 reply 0 retweets 0 likes
@rmhrisk @YuryStrozhevsky @sleevi_ Well, either Chrome or Gecko is buggy, since they don't agree. Would like to understand which one!
-
-
Replying to @really_bz
@bz_moz@YuryStrozhevsky@sleevi_ with case it js clear the RFC states it's uppercase but that seems inconsistent with other W3C APIs.0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.