From: Andreas Schwab <schwab@suse.de>
To: Oliver Welter <mail@oliwel.de>
Cc: Tavis Ormandy <taviso@sdf.lonestar.org>, gdb@sourceware.org
Subject: Re: How to protect a file from debugging
Date: Mon, 11 Jun 2007 09:32:00 -0000 [thread overview]
Message-ID: <je8xaqg7l3.fsf@sykes.suse.de> (raw)
In-Reply-To: <466D14D5.4020007@oliwel.de> (Oliver Welter's message of "Mon\, 11 Jun 2007 11\:24\:37 +0200")
Oliver Welter <mail@oliwel.de> writes:
> Ok here is what I am planing:
>
> I have an application, lets say a simple text editor, that is used to
> read/write sensitive information.
> Now I start gdb, attach it to the process and call "gcore" which - for
> my understanding - dumps the entire memory of the process to a file. So
> the core dump reveals my secret data.
Why is that a problem? You are one only reading the same secret data
that you just entered yourself in the editor.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-06-11 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 8:17 Oliver Welter
2007-06-11 9:16 ` Tavis Ormandy
2007-06-11 9:25 ` Oliver Welter
2007-06-11 9:32 ` Andreas Schwab [this message]
2007-06-11 9:38 ` Oliver Welter
2007-06-11 10:04 ` Tavis Ormandy
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=je8xaqg7l3.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sourceware.org \
--cc=mail@oliwel.de \
--cc=taviso@sdf.lonestar.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