mark-roy

Upon further research (http://openssl.6102.n7.nabble.com/stateOrProvinceName-field-problem-when-signing-CSR-td26124.html), this is probably an issue with the openssl ca utility. It should compare a PRINTABLESTRING and UTF8STRING appropriately. The workaround is to set the openssl ca...

The saga continues... PRINTABLESTRING can contain only a pretty-limited set of characters: https://en.wikipedia.org/wiki/PrintableString, which is not ideal. So, how can I get certificationRequestToPem() to produce UTF8STRING-encoded strings?

generate-csr.js uses node-forge to create a CSR whose OU contains "R&D" (note illegal PRINTABLE string character "&"), which node-forge does not complain about. When I attempt to sign it later...

@micryc Hi Michal; I see now that a version 3.0.1 spec is being generated. How do I cause it to generate version 3.1? Thanks