From: Chase Venters <chase.venters@clientec.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Subject: Re: forbid to strace a program
Date: Sat, 3 Sep 2005 17:34:19 -0500
User-Agent: KMail/1.8.1
References: <4IExJ-4aE-21@gated-at.bofh.it> <4IMY1-7C1-19@gated-at.bofh.it> <dfd7pm$1c2$1@pD9F86CE8.dip0.t-ipconnect.de>
In-Reply-To: <dfd7pm$1c2$1@pD9F86CE8.dip0.t-ipconnect.de>
Cc: linux-kernel@vger.kernel.org
Organization: Clientec, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200509031734.19190.chase.venters@clientec.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1045
Lines: 25

> Is there another way to do this? If the password is crypted, I need a
> passphrase or something other to decrypt it again. Not really a solution
> of the problem.
>
> Therefore, it would be best, to hide it by preventing stracing of the
> application to all users and root.
>
> Ok, root could search for the password directly in the memory, but this
> would be not as easy as a strace.

Obfuscation isn't really valid security. Making something 'harder' to break 
isn't a solution unless you're making it hard enough that current technology 
can't break it (eg... you always have the brute force option, but good crypto 
intends to make such an option impossible without expending zillions of clock 
cycles). 

Can I ask why you want to hide the database password from root?

Regards,
Chase Venters
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/