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 >

Java keytool certgen - Alertnative Subject Name

2017-05-23 Thread Roger Dunn
We are moving from OpenSSL to Java to handle CSRs for our CA. Our devices require a custom 'description' field as part of the Subject sequence. (Related link) https://linux.die.net/man/3/x509_name_get_text_by_nid The following command line fails (we are using a HSM but that's not relevant to