From: AUSTIN WOODARD <arwbutch@attbi.com>
To: 9fans@cse.psu.edu
Subject: [9fans] securing memory during password processing
Date: Mon, 30 Dec 2002 09:54:54 -0500 [thread overview]
Message-ID: <3E105E3E.2030900@attbi.com> (raw)
Dear Rob Pike,
Hi - my name is Austin Woodard, is was reading the P9 Security paper at
the bell labs site and came across an unsolved problem of encrytion
keys being left in memory and their being vulnerable to recovery by a
system reset using a debugger. Why not use temporary allocated space in
memory for their use and then delete at end of use by filling that space
with all 0's or FF's. this would seem to make for more secure use of
password and key handling. Although this process may add time to the
running of the process it would seem necessary to prevent unwanted
intrusions into ones computer. My e-mail address arwbutch@attbi.com and
would appreciate a reply if you have time. Thanks for taking the time to
consider this e-mail --- Austin
next reply other threads:[~2002-12-30 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 14:54 AUSTIN WOODARD [this message]
2002-12-30 15:08 David Presotto
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=3E105E3E.2030900@attbi.com \
--to=arwbutch@attbi.com \
--cc=9fans@cse.psu.edu \
/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).