From: Andrew Pinski <pinskia@gcc.gnu.org>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: gcc.gnu.org/sourceware.org SSL issues?
Date: Tue, 02 Sep 2014 02:49:00 -0000 [thread overview]
Message-ID: <CA+=Sn1no1qHizZd8kYwSaYs5awzOzTVkhXizNpR2_sJJrhwmNQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1409020317510.2958@tp.orcam.me.uk>
On Mon, Sep 1, 2014 at 7:47 PM, Maciej W. Rozycki
<macro@codesourcery.com> wrote:
> Hi,
>
> I've been looking for a statement on this matter somewhere, like on the
> front pages, but found nothing so has this issue been known? E.g. the
> last entry on http://sourceware.org/news.html is from 2005.
>
> Since about yesterday or maybe the day before I've been having problems
> accessing gcc.gnu.org and sourceware.org sites over SSL, first a security
> alert is raised about a domain mismatch like:
>
> 'You have attempted to establish a connection with "gcc.gnu.org". However,
> the security certificate presented belongs to "(cygwin.com ,
> www.cygwin.com)". It is possible, though unlikely, that someone may be
> trying to intercept your communication with this web site.'
>
> and then if I ignore this warning (knowing that cygwin.com is really the
> same machine; this used to be browser-version-specific for some reason and
> I used not to care because I don't send any sensitive information to these
> sites anyway, but now I get it with the newer version too) I get this:
>
> 'Error establishing an encrypted connection to gcc.gnu.org. Error Code:
> -8092.'
>
> and the connection then terminates. Looking up Google reveals that -8092
> corresponds to SEC_ERROR_KEYGEN_FAIL or "Unable to generate public-private
> key pair".
>
> Some parts of the sites are accessible unencrypted, however the bugzillas
> are not and the SSL issue therefore blocks some of my work. I'll
> apreciate your assistance.
What browser are you using? I have heard some older browser does not
support the feature that gcc.gnu.org uses for SSL.
Thanks,
Andrew
>
> Thanks,
>
> Maciej
next prev parent reply other threads:[~2014-09-02 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 2:47 Maciej W. Rozycki
2014-09-02 2:49 ` Andrew Pinski [this message]
2014-09-02 3:23 ` Maciej W. Rozycki
2014-09-02 6:40 ` Gerald Pfeifer
2014-09-02 14:34 ` Maciej W. Rozycki
2014-09-02 4:45 ` Hans-Peter Nilsson
2014-09-02 18:18 ` Maciej W. Rozycki
2014-09-02 14:52 ` Joseph S. 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='CA+=Sn1no1qHizZd8kYwSaYs5awzOzTVkhXizNpR2_sJJrhwmNQ@mail.gmail.com' \
--to=pinskia@gcc.gnu.org \
--cc=macro@codesourcery.com \
--cc=overseers@sourceware.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).