You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was migrated from Pagure Issue #577. Originally filed by cfu (@cfu) on 2013-04-02 22:00:37:
Closed as Invalid
Assigned to nobody
task to investigate whether the newly improved can do all we want it to do, including key archival for both RSA and ECC keys, and then later DSA keys as well.
My understanding is that is supposed to replace window.crypto.generateCRMFRequest.
So keygen was first, window.crypto.generateCRMFRequest() was made to fix some issues (and get some features like key-recovery). The new effort in I think was meant to address those issues.
I have no idea how common window.crypto.generateCRMFRequest is. Is it obsolete? Should it be removed? Does anybody have a link to a site that is using it for its intended purpose?
I don't think you can remove it for a while. Server deployments lag client features by quite a few years. Servers don't implement new features supplied in clients until they are release. This type of feature isn't quite like a normal html feature, where you can update a .hmtl file or a content manager macro. These tags are usually tied more closely to the servers that use them.
More generally, I would like to remove all the Mozilla-proprietary methods and properties from window.crypto; i.e. all the ones athttps://developer.mozilla.org/en-US/docs/JavaScript_crypto. Some of them are actually pretty problematic. Are there any worth keeping?
I'd say you probably can't do that wholesale, but you probably can review and cull this list, particularly if there are good replacements.
Thanks,
Brian
The text was updated successfully, but these errors were encountered:
The tag does not support archival. There is no suitable replacement for generateCRMFRequest at this time. At this point, I don't believe Mozilla can/will remove this, so there's nothing to do on our side. If that decision changes, we will have to revisit this.
At this point, I don't believe Mozilla can/will remove this, so there's nothing to do on our side. If that decision changes, we will have to revisit this.
This issue was migrated from Pagure Issue #577. Originally filed by cfu (@cfu) on 2013-04-02 22:00:37:
task to investigate whether the newly improved can do all we want it to do, including key archival for both RSA and ECC keys, and then later DSA keys as well.
On 04/01/2013 03:19 PM, Robert Relyea wrote:
The text was updated successfully, but these errors were encountered: