Re: Certificate OU= fields with missing O= field

2019-11-01 Thread Jakob Bohm via dev-security-policy
ecurity-policy Sent: Friday, November 1, 2019 9:13 AM To: Kurt Roeckx mailto:k...@roeckx.be>> Cc: Matthias van de Meent mailto:matthias.vandeme...@cofano.nl>>; MDSP mailto:dev-security-policy@lists.mozilla.org>> Subject: Re: Certificate OU= fields with missing O= field On Fri,

Re: Certificate OU= fields with missing O= field

2019-11-01 Thread Ryan Sleevi via dev-security-policy
*Cc:* mozilla-dev-security-policy < > mozilla-dev-security-pol...@lists.mozilla.org> > *Subject:* Re: Certificate OU= fields with missing O= field > > > > Is your view that the OU is not Subject Identity Information, despite that > being the Identity Information tha

RE: Certificate OU= fields with missing O= field

2019-11-01 Thread Jeremy Rowley via dev-security-policy
Rowley Cc: mozilla-dev-security-policy Subject: Re: Certificate OU= fields with missing O= field Is your view that the OU is not Subject Identity Information, despite that being the Identity Information that appears in the Subject? Are there other fields and values that you believe are not SII

RE: Certificate OU= fields with missing O= field

2019-11-01 Thread Robin Alden via dev-security-policy
> -Original Message- > From: Kurt Roeckx via dev-security-policy > Sent: 01 November 2019 10:15 > To: Matthias van de Meent > Cc: MDSP > Subject: Re: Certificate OU= fields with missing O= field > > On Fri, Nov 01, 2019 at 11:08:23AM +0100, Matthias van de M

Re: Certificate OU= fields with missing O= field

2019-11-01 Thread Ryan Sleevi via dev-security-policy
hias van de Meent ; MDSP < > dev-security-policy@lists.mozilla.org> > Subject: Re: Certificate OU= fields with missing O= field > > On Fri, Nov 1, 2019 at 5:14 AM Kurt Roeckx via dev-security-policy < > dev-security-policy@lists.mozilla.org> wrote: > > > > On Fri, Nov 01, 20

RE: Certificate OU= fields with missing O= field

2019-11-01 Thread Jeremy Rowley via dev-security-policy
to the O field information as long as the information is verified. -Original Message- From: dev-security-policy On Behalf Of Alex Cohn via dev-security-policy Sent: Friday, November 1, 2019 9:13 AM To: Kurt Roeckx Cc: Matthias van de Meent ; MDSP Subject: Re: Certificate OU= fields

Re: Certificate OU= fields with missing O= field

2019-11-01 Thread Alex Cohn via dev-security-policy
On Fri, Nov 1, 2019 at 5:14 AM Kurt Roeckx via dev-security-policy wrote: > > On Fri, Nov 01, 2019 at 11:08:23AM +0100, Matthias van de Meent via > dev-security-policy wrote: > > Hi, > > > > I recently noticed that a lot of leaf certificates [0] have > > organizationalUnitName specified without

Re: Certificate OU= fields with missing O= field

2019-11-01 Thread Matthias van de Meent via dev-security-policy
Hi, I was notified that the attachments were lost in transmission, so here are the links: cert_no_dcv: https://drive.google.com/open?id=1s43AaW5lCkSzbr-If6l2F_gwLkwDVy6w cert_by_issuer_no_dcv: https://drive.google.com/open?id=1-er8R2CfcG8CRK4I3KUXnv8PDgGQKc1Y cert_by_issuer_name_no_dcv:

Re: Certificate OU= fields with missing O= field

2019-11-01 Thread Kurt Roeckx via dev-security-policy
On Fri, Nov 01, 2019 at 11:08:23AM +0100, Matthias van de Meent via dev-security-policy wrote: > Hi, > > I recently noticed that a lot of leaf certificates [0] have > organizationalUnitName specified without other organizational > information such as organizationName. Many times this field is