From: Oliver Welter <mail@oliwel.de>
To: Andreas Schwab <schwab@suse.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:38:00 -0000 [thread overview]
Message-ID: <466D17E4.8070703@oliwel.de> (raw)
In-Reply-To: <je8xaqg7l3.fsf@sykes.suse.de>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
>> 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.
>
Before the editor can access the data, its integrity is checked and the
editor has certain properties, e.g. not allowing to store the data
outside of an encrypted filesystem. So if an unchecked application can
gather the data, it might leave the system.
Oliver
--
Protect your environment - close windows and adopt a penguin!
PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-11 9:38 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
2007-06-11 9:38 ` Oliver Welter [this message]
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=466D17E4.8070703@oliwel.de \
--to=mail@oliwel.de \
--cc=gdb@sourceware.org \
--cc=schwab@suse.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