Re: mailops https breakage
In articleyou write: >> Fun fact about letsencrypt certs, they expire after a month or so. > >90 days Well, yes. That's why highly skilled and experienced administrators such as yourself set up the automatic renewal scripts at the same time they install the initial cert, right? I use the acme.sh shell script. It ain't hard. R's, John
Re: mailops https breakage
Both. Either. Take your pick Ed Pers From: Seth Mattinen Sent: Tuesday, June 20, 8:06 PM Subject: Re: mailops https breakage To: nanog@nanog.org On 6/20/17 16:57, Keith Medcalf wrote: > How else would one maintain government control over free encryption certificates? So Let's Encrypt is run by the Illuminati now? Or is it Freemasons? It's hard to keep track.
Re: mailops https breakage
On 6/20/17 16:57, Keith Medcalf wrote: How else would one maintain government control over free encryption certificates? So Let's Encrypt is run by the Illuminati now? Or is it Freemasons? It's hard to keep track.
Re: mailops https breakage
> How else would one maintain government control over free encryption > certificates? black helicopters
RE: mailops https breakage
How else would one maintain government control over free encryption certificates? -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı > -Original Message- > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Randy Bush > Sent: Tuesday, 20 June, 2017 17:34 > To: Edwin Pers > Cc: NANOG list > Subject: Re: mailops https breakage > > > Fun fact about letsencrypt certs, they expire after a month or so. > > 90 days
Re: mailops https breakage
> Fun fact about letsencrypt certs, they expire after a month or so. 90 days
RE: mailops https breakage
Fun fact about letsencrypt certs, they expire after a month or so. Looks like the site admin never noticed/cared to update it (since 2016), even though there's a nice little helper program to auto-update them that you can throw in a cronjob (or scheduled task, if you're into IIS) and forget about Ed Pers -Original Message- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Lyndon Nerenberg Sent: Sunday, June 11, 2017 6:27 PM To: NANOG list <nanog@nanog.org> Subject: mailops https breakage > On Aug 27, 2016, at 6:46 PM, Matt Palmer <mpal...@hezmatt.org> wrote: > > On Sat, Aug 27, 2016 at 01:25:42AM -, John Levine wrote: >> In article >> <caltoqtqkfeadxnr1+4yzydoyuwebg_+qyaq7ubhxtmv0jcn...@mail.gmail.com> you >> write: >>> I was working within the limits of what I had available. >> >> Here's the subscription page for mailop. It's got about as odd a mix >> of people as nanog, ranging from people with single user linux >> machines to people who run some of the largest mail systems in the >> world, including Gmail: >> >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > > I know they're mailops, and not tlsops, but surely presenting a cert > that didn't expire six months ago isn't beyond the site admin's capabilities? I tried again, ten months later. Still broken :-( Is there a replacement site I'm missing out on?
mailops https breakage
> On Aug 27, 2016, at 6:46 PM, Matt Palmerwrote: > > On Sat, Aug 27, 2016 at 01:25:42AM -, John Levine wrote: >> In article >> you >> write: >>> I was working within the limits of what I had available. >> >> Here's the subscription page for mailop. It's got about as odd >> a mix of people as nanog, ranging from people with single user linux >> machines to people who run some of the largest mail systems in >> the world, including Gmail: >> >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > > I know they're mailops, and not tlsops, but surely presenting a cert that > didn't expire six months ago isn't beyond the site admin's capabilities? I tried again, ten months later. Still broken :-( Is there a replacement site I'm missing out on?