From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: forbid to strace a program
Date: Sun, 04 Sep 2005 17:47:28 -0400 [thread overview]
Message-ID: <200509042147.j84LlSl3020442@laptop11.inf.utfsm.cl> (raw)
In-Reply-To: Message from Andreas Hartmann <andihartmann@01019freenet.de> of "Sun, 04 Sep 2005 00:23:50 +0200." <dfd7pm$1c2$1@pD9F86CE8.dip0.t-ipconnect.de>
Andreas Hartmann <andihartmann@01019freenet.de> wrote:
1> Alex Riesen wrote:
> > On 9/3/05, Andreas Hartmann <andihartmann@01019freenet.de> wrote:
> >> Hello!
> >> Is it possible to prevent a program to be straced on x86?
> >> What do I have to do, eg., to prevent a perl-program to be straced?
Look at the contortions shc does for this.
> > So that none can see what are you doing? Or because your program is
> > breaking because of this? Probably nothing, but someone would like
> > to know what it is you are doing and exactly how it breaks (and, if
> > you don't mind -
> > why it breaks).
> That's not really the problem. I want to hide a clear text password in
> that program (something like ssh-agent or gpg-agent; the last can be
> straced, too :-() which I need for a database when the program runs.
Anyone who can read the executable can find that out. In the worst case, by
running it in a doctored environment that catches the password.
Place it in a file that noone else can read, that way it is also easier to
change.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
next prev parent reply other threads:[~2005-09-04 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4IExJ-4aE-21@gated-at.bofh.it>
[not found] ` <4IMY1-7C1-19@gated-at.bofh.it>
2005-09-03 22:23 ` Andreas Hartmann
2005-09-03 22:34 ` Chase Venters
2005-09-04 21:47 ` Horst von Brand [this message]
[not found] <4IOGw-1DU-11@gated-at.bofh.it>
[not found] ` <4IOGw-1DU-13@gated-at.bofh.it>
[not found] ` <4IOGw-1DU-9@gated-at.bofh.it>
[not found] ` <4IOQc-1Pk-23@gated-at.bofh.it>
2005-09-04 7:32 ` Andreas Hartmann
2005-09-04 8:45 ` Willy Tarreau
2005-09-04 8:47 ` Tejun Heo
2005-09-05 9:36 ` Bernd Petrovitsch
2005-09-03 11:28 Andreas Hartmann
2005-09-03 20:29 ` Alex Riesen
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=200509042147.j84LlSl3020442@laptop11.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=andihartmann@01019freenet.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®