On Tuesday, October 2, 2018 at 7:02:32 AM UTC-7, Dimitris Zacharopoulos wrote:
> On 1/10/2018 8:15 μμ, Ryan Sleevi via dev-security-policy wrote:
> > On Mon, Oct 1, 2018 at 9:21 AM Dimitris Zacharopoulos
> > wrote:
>
> > [...]
> >
> >
> >> I am certainly not suggesting that CAs should put inaccur
Thank you Yves. I do not have any other questions, and I do not believe
that any further actions are required.
- Wayne
On Mon, Oct 1, 2018 at 8:07 AM Yves Nullens
wrote:
> Wayne,
>
>
>
> I confirm that the only change following this investment is the update of
> the overview chapter.
>
>
>
> Be
On 2/10/2018 5:21 μμ, Ryan Sleevi via dev-security-policy wrote:
On Tue, Oct 2, 2018 at 10:02 AM Dimitris Zacharopoulos
wrote:
But this inaccurate data is not used in the validation process nor
included in the certificates. Perhaps I didn't describe my thoughts
accurately. Let me have anothe
On Tue, Oct 2, 2018 at 10:02 AM Dimitris Zacharopoulos
wrote:
> >> But this inaccurate data is not used in the validation process nor
> >> included in the certificates. Perhaps I didn't describe my thoughts
> >> accurately. Let me have another try using my previous example. Consider
> an
> >> Inf
On 1/10/2018 8:15 μμ, Ryan Sleevi via dev-security-policy wrote:
On Mon, Oct 1, 2018 at 9:21 AM Dimitris Zacharopoulos
wrote:
[...]
I am certainly not suggesting that CAs should put inaccurate and
misleading information in certificates :-) I merely said that if the
Subscriber introduces
On 01/10/2018 16:51, Rob Stradling via dev-security-policy wrote:
Hi Iñigo.
I suspect it's because my script that produces the 1 week summary data
[1] isn't using a consistent view of the underlying linting results
throughout its processing. Hopefully this [2] will fix it.
Doh. [2] was ine
6 matches
Mail list logo
