Re: Specifying allowed parameter encodings in Mozilla policy

2017-06-05 Thread Hubert Kario
On Friday, 19 May 2017 15:57:18 CEST Gervase Markham wrote: > Brian Smith filed two issues on our Root Store Policy relating to making > specific requirements of the technical content of certificates: > > "Specify allowed PSS parameters" > https://github.com/mozilla/pkipolicy/issues/37 > >

Re: Specifying allowed parameter encodings in Mozilla policy

2017-05-23 Thread Gervase Markham
On 23/05/17 14:08, ryan.sle...@gmail.com wrote: > I think it should be a policy OK. Are you able to propose wording and a location within the policy (section 5.1) for both of these proposals? If you are willing to do that, I'm happy to include it. Gerv -- dev-tech-crypto mailing list

Re: Specifying allowed parameter encodings in Mozilla policy

2017-05-23 Thread ryan . sleevi
On Monday, May 22, 2017 at 3:58:21 AM UTC-4, Gervase Markham wrote: > 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 >

Re: Specifying allowed parameter encodings in Mozilla policy

2017-05-22 Thread Gervase Markham
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

Re: Specifying allowed parameter encodings in Mozilla policy

2017-05-19 Thread Ryan Sleevi
I support both of those requirements, so that we can avoid it on a 'problematic practices' side :) 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 :) On Fri, May 19, 2017 at 9:57 AM,