From: Andy Wingo <wingo@pobox.com>
To: Lizzie Dixon <_@lizzie.io>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Guile security vulnerability w/ listening on localhost + port (with fix)
Date: Sun, 26 Feb 2017 19:22:31 +0100 [thread overview]
Message-ID: <87k28cu80o.fsf@pobox.com> (raw)
In-Reply-To: <20161014215551.GA31883@lizzie.io> (Lizzie Dixon's message of "Fri, 14 Oct 2016 14:55:51 -0700")
Hi!
On Fri 14 Oct 2016 23:55, Lizzie Dixon <_@lizzie.io> writes:
> <https://blog.lizzie.io/exploiting-CVE-2016-8606.html>
I know it's a late kudo but still -- great investigation and writeup,
thank you for digging in to this one :)
Andy
prev parent reply other threads:[~2017-02-26 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 14:01 Guile security vulnerability w/ listening on localhost + port (with fix) Christopher Allan Webber
2016-10-12 15:49 ` Nala Ginrut
2016-10-12 16:11 ` Thompson, David
2016-10-14 21:55 ` Lizzie Dixon
2016-10-16 15:05 ` Christopher Allan Webber
2016-10-16 19:51 ` Arne Babenhauserheide
2016-10-17 1:39 ` Lizzie Dixon
2017-02-26 18:22 ` Andy Wingo [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k28cu80o.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=_@lizzie.io \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.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).