From: "Rémi Cardona" <remi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Akamai secure memory allocator for OpenSSL?
Date: Mon, 14 Apr 2014 23:12:52 +0200 [thread overview]
Message-ID: <1397509972.27093.2.camel@localhost> (raw)
In-Reply-To: <534BA0E3.5010609@gentoo.org>
Le lundi 14 avril 2014 à 10:48 +0200, Tiziano Müller a écrit :
> Not really, no. I would rather wait until other people have reviewed
> and/or it has been pulled into openssl.
>
> To cite the Akamai dev who posted the patch [1]:
> "Let me restate that: *do not just take this patch and put it into
> production without careful review.*"
http://lekkertech.net/akamai.txt
I, for one, am glad we didn't pull this in right away. OpenSSL is under
a lot of scrutiny now, so let's not rush any patches.
Cheers
Rémi
next prev parent reply other threads:[~2014-04-14 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 20:42 [gentoo-dev] Akamai secure memory allocator for OpenSSL? Joshua Kinard
2014-04-14 0:17 ` Patrick Lauer
2014-04-14 1:27 ` Joshua Kinard
2014-04-14 8:48 ` Tiziano Müller
2014-04-14 21:12 ` Rémi Cardona [this message]
2014-04-21 19:19 ` Toralf Förster
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=1397509972.27093.2.camel@localhost \
--to=remi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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