public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Lisa Marie Maginnis <lisam@fsf.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@gcc.gnu.org, ruben@fsf.org
Subject: URGENT! SSL Cert for gcc.gnu.org
Date: Thu, 02 Jun 2016 13:44:00 -0000	[thread overview]
Message-ID: <20160602134418.GA13284@pegasus.office.fsf.org> (raw)
In-Reply-To: <20160527203522.GB30724@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

The cert expires *today*, I noticed the cert on gcc.gnu.org is still
the old gandi cert. Do you need us to renew it for you? Or were you
able to generate a letsencrypt certificate (prefered).

Let me know, if you need to call me: : +1-617-542-5942 ex/11

Thanks!

On Fri, May 27, 2016 at 04:35:22PM -0400, Frank Ch. Eigler wrote:
> Hi -
> 
> > The FSF and GNU Project are switching to the Lets Encrypt CA for
> > certificate generation. The SSL Cert that the FSF buys for gcc.gnu.org
> > will be expiring in the next week or so. Could an admin please install
> > LetsEncrypt on gcc.gnu.org and obtian a certificate? [...]
> 
> Will do.
> 
> - FChE
> 

-- 
~Lisa Marie Maginnis
Senior System Administrator
Free Software Foundation
http://fsf.org http://gnu.org
GPG Key: 61EEC710

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-06-02 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 14:16 Lisa Marie Maginnis
2016-05-27 20:35 ` Frank Ch. Eigler
2016-06-02 13:44   ` Lisa Marie Maginnis [this message]
2016-06-02 15:54     ` URGENT! " Frank Ch. Eigler
2016-06-02 16:56       ` Joseph Myers

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=20160602134418.GA13284@pegasus.office.fsf.org \
    --to=lisam@fsf.org \
    --cc=fche@redhat.com \
    --cc=overseers@gcc.gnu.org \
    --cc=ruben@fsf.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 read-only IMAP folder(s) and NNTP newsgroup(s).