[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Letsencrypt

Subject: Letsencrypt
From: edward.dore at freethought-internet.co.uk (Edward Dore)
Date: Mon, 30 Jul 2018 20:02:06 +0000
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <CAEE+rGpT2uo3jJi5VT=cOitsYcbZGUPAqXKy854qN9hhozxDbw@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]>

It's just been fixed - see https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/5b5f5aa93a343f54d7982864.

Edward Dore 
Freethought Internet

ï»¿On 30/07/2018, 21:01, "NANOG on behalf of Alexander Maassen" <nanog-bounces at nanog.org on behalf of outsider at scarynet.org> wrote:

    As most of you noticed, the domain letsencrypt.org is on clientHold,
    does anyone have more information as of why this is the case ?

Follow-Ups:
- Letsencrypt
  - From: outsider at scarynet.org (Alexander Maassen)

References:
- California fires: smart speakers and emergency alerts
  - From: sean at donelan.com (Sean Donelan)
- California fires: smart speakers and emergency alerts
  - From: aaron at heyaaron.com (Aaron C. de Bruyn)
- California fires: smart speakers and emergency alerts
  - From: lou at metron.com (Lou Katz)
- California fires: smart speakers and emergency alerts
  - From: sean at donelan.com (Sean Donelan)
- Letsencrypt
  - From: outsider at scarynet.org (Alexander Maassen)

Prev by Date: Security team objectives
Next by Date: Letsencrypt
Previous by thread: Letsencrypt
Next by thread: Letsencrypt
Index(es):
- Date
- Thread