From: "Frank Ch. Eigler" <fche@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: SVN and SHA-1 hash
Date: Fri, 03 Mar 2017 14:09:00 -0000 [thread overview]
Message-ID: <20170303140909.GD16375@redhat.com> (raw)
In-Reply-To: <CA+=Sn1m2uAriOC+mcY576a3qNW_NN9M+oB3NK0HQn3uGnFjg+A@mail.gmail.com>
Hi -
> https://arstechnica.com/security/2017/02/watershed-sha1-collision-just-broke-the-webkit-repository-others-may-follow/
>
> Even though we trust our users., it might be useful to make sure we
> put in the hook to the current svn repos; I think gcc is the only one.
That could be a good idea - take it gcc@ and/or those operating the
gccadmin account here.
- FChE
prev parent reply other threads:[~2017-03-03 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 7:40 Andrew Pinski
2017-03-03 14:09 ` Frank Ch. Eigler [this message]
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=20170303140909.GD16375@redhat.com \
--to=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=pinskia@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.
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).