On Sun, Jan 14, 2024 at 9:12 PM Aaron Gable wrote:
> On Sun, Jan 14, 2024, 10:12 Rob Sayre wrote:
>
>> On Sun, Jan 14, 2024 at 3:01 AM Deb Cooley wrote:
>>
>>> I had this marked as 'hold for update' (vs. 'verified'). I can't tell
>>> from the discussion how you think we should be handling it.
On Sun, Jan 14, 2024, 10:12 Rob Sayre wrote:
> On Sun, Jan 14, 2024 at 3:01 AM Deb Cooley wrote:
>
>> I had this marked as 'hold for update' (vs. 'verified'). I can't tell
>> from the discussion how you think we should be handling it.
>>
>
> The erratum says "the challenge must be initiated
On Sun, Jan 14, 2024 at 3:01 AM Deb Cooley wrote:
> I had this marked as 'hold for update' (vs. 'verified'). I can't tell
> from the discussion how you think we should be handling it.
>
The erratum says "the challenge must be initiated over HTTP, not HTTPS.",
which is a little better than the
Google bought the gTLD of .dev and .app and set HSTS on tld level.
On 2024년 1월 14일 오후 8시 1분 4초 GMT+09:00, Deb Cooley 작성함:
>I had this marked as 'hold for update' (vs. 'verified'). I can't tell from
>the discussion how you think we should be handling it.
>
>I'm also not sure why .dev domains are
I had this marked as 'hold for update' (vs. 'verified'). I can't tell from
the discussion how you think we should be handling it.
I'm also not sure why .dev domains are being discussed. How are .dev
domains obtaining test certificates (because one should not be issuing
operational certificates,
