linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Sandy Harris <sandyinchina@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: memset() in crypto code?
Date: Mon, 6 Oct 2014 14:23:45 -0400	[thread overview]
Message-ID: <20141006182345.GC14468@titan.lakedaemon.net> (raw)
In-Reply-To: <CACXcFmmv2hKaVNS3hok6V=7VmrqTMF1_Pn2z0e31dd_YywBfKQ@mail.gmail.com>

On Mon, Oct 06, 2014 at 01:59:06PM -0400, Sandy Harris wrote:
> On Mon, Oct 6, 2014 at 1:44 PM, Jason Cooper <jason@lakedaemon.net> wrote:
> 
> > On Sat, Oct 04, 2014 at 11:09:40PM -0400, Sandy Harris wrote:
> >> There was recently a patch to the random driver to replace memset()
> >> because, according to the submitter, gcc sometimes optimises memset()
> >> away which might leave data unnecessarily exposed. The solution
> >> suggested was a function called memzero_explicit(). There was a fair
> >> bit of discussion and the patch was accepted.
> >
> > Do you have a pointer?
> 
> https://lkml.org/lkml/2014/8/25/497

Ok, that was the same thread I found.  I was looking for the 'fair bit
of discussion' part. ;-)

thx,

Jason.

  reply	other threads:[~2014-10-06 18:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05  3:09 memset() in crypto code? Sandy Harris
2014-10-05 10:33 ` Daniel Borkmann
2014-10-06 17:44 ` Jason Cooper
2014-10-06 17:59   ` Sandy Harris
2014-10-06 18:23     ` Jason Cooper [this message]
2014-10-06 18:52   ` Sandy Harris
2014-10-06 19:02     ` Daniel Borkmann
2014-10-08  2:30       ` Sandy Harris
2014-10-08  7:18         ` Daniel Borkmann

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=20141006182345.GC14468@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=sandyinchina@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 NNTP newsgroup(s).