From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/tor: security bump to 0.3.5.8
Date: Fri, 15 Mar 2019 15:58:53 +0100 [thread overview]
Message-ID: <87ef78b2vm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190223075029.1838-1-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Sat, 23 Feb 2019 08:50:29 +0100")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> Release notes:
> https://blog.torproject.org/new-releases-tor-0402-alpha-0358-03411-and-03312
> Fixes CVE-2019-8955:
> KIST can write above outbuf highwater mark
> https://trac.torproject.org/projects/tor/ticket/29168
> Updated license hash after upstream commit
> https://gitweb.torproject.org/tor.git/commit/LICENSE?h=maint-0.3.5&id=efe55b88987c2539c218fdf1f46f16f9bdc3a8eb
> which bumps copyright date to 2019.
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Instead of cherry picking this, I have instead bumped the version to
0.3.4.11 for 2018.11.x.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-03-15 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 7:50 [Buildroot] [PATCH 1/1] package/tor: security bump to 0.3.5.8 Bernd Kuhls
2019-02-23 8:54 ` Peter Korsgaard
2019-03-15 14:58 ` Peter Korsgaard [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=87ef78b2vm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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