From: Cheryl Wheeler <c_wheeler_2002@yahoo.ca>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: 23948@debbugs.gnu.org
Subject: bug#23948: Expired Certificate on gnu.org
Date: Mon, 11 Jul 2016 18:58:49 -0400 [thread overview]
Message-ID: <844aa085-463d-c17d-d274-eaf6da2e6716@yahoo.ca> (raw)
In-Reply-To: <CAAF+z6G4KAa474ixrbXHurGu_t=jp5ZQjSwZHbbd5n1Lmzn=1Q@mail.gmail.com>
Hi,
I was using the HTTPS Everywhere extension in Firefox when I encountered
the issue. However, I disabled it and tried again before I reported the
problem, because it has been known to occasionally cause issues on
sites. :-)
Just now I tried it in IE 11, no problem there. IE does not insist on
using HTTPS for lists.gnu.org. Maybe a Firefox issue?
I will report the certificate issue to the webmaster.
Cheryl
On 11/07/2016 6:46 PM, Xue Fuqiao wrote:
> On Tue, Jul 12, 2016 at 1:37 AM, Cheryl Wheeler <c_wheeler_2002@yahoo.ca> wrote:
>> Hi,
> Hi Cheryl,
>
>> I was browsing the site at this page
>> (https://www.gnu.org/software/emacs/history.html), and I found that clicking
>> any of the links caused my browser to show the following error:
>>
>> "lists.gnu.org uses an invalid security certificate. The certificate expired
>> on July-11-16 11:02 AM. The current time is July-11-16 1:33 PM. Error code:
>> SEC_ERROR_EXPIRED_CERTIFICATE"
> Are you using extensions like HTTPS Everywhere? I do not see the
> certificate date error because the links on this page are not encrypted
> by SSL/TLS.
>
> Anyway, the certificate does seem to have a problem. Can you report it
> to webmasters@gnu.org? Thank you.
next prev parent reply other threads:[~2016-07-11 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 17:37 bug#23948: Expired Certificate on gnu.org Cheryl Wheeler
2016-07-11 22:46 ` Xue Fuqiao
2016-07-11 22:58 ` Cheryl Wheeler [this message]
2016-07-12 4:33 ` Eli Zaretskii
2016-07-12 5:11 ` Richard Stallman
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=844aa085-463d-c17d-d274-eaf6da2e6716@yahoo.ca \
--to=c_wheeler_2002@yahoo.ca \
--cc=23948@debbugs.gnu.org \
--cc=xfq.free@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.