From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: git.gnus.org certificates
Date: Thu, 01 Aug 2013 18:19:55 +0200 [thread overview]
Message-ID: <878v0l8jtg.fsf@dod.no> (raw)
In-Reply-To: <m361vpbdgf.fsf@stories.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Simon Josefsson <simon@josefsson.org> writes:
>> It will expire tomorrow. Here is a new one, for the same private key so
>> just replace the old one with this one and things will just work.
>>
>> /Simon
>>
>> -----BEGIN CERTIFICATE-----
> Thanks. Did somebody else install this, or should I do that now?
Seeing that Simon's email was sent 20 weeks 2 days and 13 hours ago, the
"new" cert could potentially be ready to expire at any time now...
next prev parent reply other threads:[~2013-08-01 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 3:13 Simon Josefsson
2013-08-01 16:09 ` Lars Magne Ingebrigtsen
2013-08-01 16:19 ` Steinar Bang [this message]
2013-08-01 16:33 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878v0l8jtg.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).