From: Dan Rosenberg <drosenberg@vsecurity.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [CRYPTO] obfuscating kernel pointers
Date: Fri, 12 Nov 2010 14:03:15 -0500 [thread overview]
Message-ID: <1289588595.3090.331.camel@Dan> (raw)
In-Reply-To: <20101112185413.GB26217@hmsreliant.think-freely.org>
> >
> adding a consistent random value to a your void * pointers sounds like a fine
> solution to the problem, then. As long as you use the same random value for the
> lifetime of the system, that will give you consistent values. And you have to
> use the same random input consistently to have consistent output on multiple
> concatinations of the same file anyway. This also has the advantage of not
> having to do a crypto operation for every print/seq_sprintf/etc that contains a
> %p.
>
The problem with that is the ease with which one could infer that random
value makes the whole thing pretty pointless.
-Dan
next prev parent reply other threads:[~2010-11-12 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 13:32 [CRYPTO] obfuscating kernel pointers Dan Rosenberg
2010-11-12 17:27 ` Neil Horman
2010-11-12 17:39 ` Dan Rosenberg
2010-11-12 18:54 ` Neil Horman
2010-11-12 19:03 ` Dan Rosenberg [this message]
2010-11-15 8:43 ` Tomas Mraz
2010-11-15 11:21 ` Neil Horman
2010-11-15 11:58 ` Herbert Xu
2010-11-15 12:06 ` Tomas Mraz
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=1289588595.3090.331.camel@Dan \
--to=drosenberg@vsecurity.com \
--cc=linux-crypto@vger.kernel.org \
--cc=nhorman@tuxdriver.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