From: Leo Famulari <leo@famulari.name>
To: contact.ng0@cryptolab.net
Cc: guix-devel@gnu.org
Subject: Re: tor: update to 0.2.9.9
Date: Tue, 24 Jan 2017 14:07:26 -0500 [thread overview]
Message-ID: <20170124190726.GB6110@jasmine> (raw)
In-Reply-To: <20170124111934.16080-1-contact.ng0@cryptolab.net>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On Tue, Jan 24, 2017 at 11:19:33AM +0000, contact.ng0@cryptolab.net wrote:
> Changes in version 0.2.9.9 - 2017-01-23
> o Major bugfixes (security):
> - Downgrade the "-ftrapv" option from "always on" to "only on when
> --enable-expensive-hardening is provided." This hardening option,
> like others, can turn survivable bugs into crashes -- and having
> it on by default made a (relatively harmless) integer overflow bug
> into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
> bugfix on 0.2.9.1-alpha.
I'm not familiar with Tor's build system.
Should we build Tor with "--enable-expensive-hardening"?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-24 19:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 11:19 tor: update to 0.2.9.9 contact.ng0
2017-01-24 11:19 ` [PATCH] gnu: tor: Update " contact.ng0
2017-01-24 19:06 ` Leo Famulari
2017-01-24 19:07 ` Leo Famulari [this message]
2017-01-24 20:56 ` Hardening (was: Re: tor: update to 0.2.9.9) ng0
2017-01-24 21:02 ` Leo Famulari
2017-01-24 21:09 ` ng0
2017-01-24 21:18 ` ng0
2017-01-24 21:32 ` Leo Famulari
2017-01-24 21:56 ` ng0
2017-01-24 22:14 ` ng0
2017-01-25 13:04 ` Hardening Ludovic Courtès
2017-01-30 12:05 ` Hardening ng0
2017-01-30 12:16 ` Hardening ng0
2017-01-25 9:09 ` Hardening (was: Re: tor: update to 0.2.9.9) Ricardo Wurmus
2017-01-25 11:51 ` Hardening ng0
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170124190726.GB6110@jasmine \
--to=leo@famulari.name \
--cc=contact.ng0@cryptolab.net \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).