From: Oliver Welter <mail@oliwel.de>
To: gdb@sourceware.org
Subject: How to protect a file from debugging
Date: Mon, 11 Jun 2007 08:17:00 -0000 [thread overview]
Message-ID: <466D04E1.4010905@oliwel.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Hi List,
sorry if this is a stupid question but I am not very familiar with gdb ;)
I am planing a security application and gdb is causing some "troubles".
Can someone point me to some infos or shortly explain me if there is a
way to protect a program from attaching to it? I must either prevent gdb
(or similar software) from attaching to a process or at least detect
the attach and send a terminate signal to the application.
best regards
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 reply other threads:[~2007-06-11 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 8:17 Oliver Welter [this message]
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
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=466D04E1.4010905@oliwel.de \
--to=mail@oliwel.de \
--cc=gdb@sourceware.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