From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: <overseers@sourceware.org>
Subject: Re: gcc.gnu.org/sourceware.org SSL issues?
Date: Tue, 02 Sep 2014 18:18:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1409021534070.2958@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.BSF.2.02.1409020036510.65173@arjuna.pair.com>
On Tue, 2 Sep 2014, Hans-Peter Nilsson wrote:
> It would be nice to know *what* has changed in the setup.
> (Is only AES 256-bit allowed these days? Pointer to advisory?)
256-bit AES is on the list of available (and enabled) ciphers in my 1.0.9
browser, so it must be something else. As to 3.5.19 I don't know offhand
how to figure out which ciphers it supports let alone disable them or
enable (speaking of UI changes...).
Maciej
next prev parent reply other threads:[~2014-09-02 18:18 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
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 [this message]
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=alpine.DEB.1.10.1409021534070.2958@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=hp@bitrange.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).