Re: Specifying allowed parameter encodings in Mozilla policy
Gervase Markham <[email protected]>
| Newsgroups | gmane.comp.mozilla.crypto |
|---|---|
| Message-ID | <[email protected]> |
On 19/05/17 17:02, Ryan Sleevi wrote: > I support both of those requirements, so that we can avoid it on a > 'problematic practices' side :) But you think this should be a policy requirement, not a Problematic Practice? https://wiki.mozilla.org/CA/Forbidden_or_Problematic_Practices > There's a webcompat aspect for deprecation - but requiring RFC-compliant > encoding (PKCS#1 v1.5) or 'not stupid' encoding (PSS) is a good thing for > the Web :) Sure. I guess I'm hoping an NSS engineer or someone else can tell us how we can measure the webcompat impact. Does it require scanning a big corpus of certs? Gerv -- dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto