Brian Smith schrieb: > Yes, I am interested in hearing why you think we cannot remove these > functions.
Well, it would be nice to have an alternative API. If you force us to move from signText to some other stuff outside Firefox, I'll doubt we'll switch to WebCryptoAPI again... . http://www.w3.org/TR/WebCryptoAPI isn't even ready for implementation, right? Will there be a method signWithUserConfirmation? (https://wiki.mozilla.org/Privacy/Features/DOMCryptAPISpec) > Instead, I would like to figure out what, if any, alternative to > signText we can provide, and also what we need to do to enhance our > <kegen> implementation to help websites migrate away from > generateCRMFRequest. > > I am very curious, in particular, what products that use > generateCRMFRequest and/or signText do for other browsers, especially > Chrome. signText: CAPICOM.SignedData in IE. "Not supported" in Chrome and Opera. Juergen -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
