From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: New extension: CRYPT target Date: Tue, 23 May 2006 19:07:21 +0200 Message-ID: <44734149.2040900@trash.net> References: <44708E68.9080508@speedy.com.ar> <44709CFC.7050007@gmx.net> <4470D859.7000706@speedy.com.ar> <4470E716.1090001@gmx.net> <44724DFE.5030806@speedy.com.ar> <4473380F.5050102@speedy.com.ar> <44733C72.1020008@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Gervasio Bernal , netfilter-devel@lists.netfilter.org Return-path: To: Carl-Daniel Hailfinger In-Reply-To: <44733C72.1020008@gmx.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Carl-Daniel Hailfinger wrote: > Gervasio Bernal wrote: > >>One possible solution would be to use a file to store the key, and chmod >>that file.That would be correct? > > > No. Still leaves a race. You have to chmod the file before you store the > key in it. Then it would be ok. You are both very wrong :) What prevents someone from opening it before the chmod, and read it afterwards? This is what umask is for ..