Dear Wayne,
Our two customers requested to use original CSR to issue two shorter
validity SSL certificates. By the re-issuance function of a program, to insert
original applications data, our SSL RA Officers checked the addresses but they
forgot to add L in Subject DN. So there are two SSL C
On Sat, Jul 07, 2018 at 10:43:26AM +0200, Kurt Roeckx via dev-security-policy
wrote:
> On Sat, Jul 07, 2018 at 01:23:24AM +, Peter Gutmann via
> dev-security-policy wrote:
> >
> > So for certlint I'd always warn for T61String with anything other than ASCII
> > (which century are they living
On Sat, Jul 7, 2018 at 4:07 AM, Kurt Roeckx via dev-security-policy <
dev-security-policy@lists.mozilla.org> wrote:
> On Fri, Jul 06, 2018 at 02:43:45PM -0700, Peter Bowen via
> dev-security-policy wrote:
> > In reviewing a recent CA application, the question came up of what is
> > allowed in a ce
On Sat, Jul 07, 2018 at 01:23:24AM +, Peter Gutmann via dev-security-policy
wrote:
>
> So for certlint I'd always warn for T61String with anything other than ASCII
> (which century are they living in? Point them at UTF8 and tell them to come
> back when they've implemented it), treat it as a
On Fri, Jul 06, 2018 at 02:43:45PM -0700, Peter Bowen via dev-security-policy
wrote:
> In reviewing a recent CA application, the question came up of what is
> allowed in a certificate in data encoded as "TeletexString" (which is
> also sometimes called T61String).
>
> Specifically, certlint will
5 matches
Mail list logo