linux-kernel - Re: [patch] Adding Secure Deletion to UBIFS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Feb 2012 19:25:08 +0200
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Joel Reardon <joel@...mbassador.com>
Cc:	linux-mtd@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] Adding Secure Deletion to UBIFS

On Thu, 2012-02-09 at 16:24 +0100, Joel Reardon wrote:
> 
> Each data nodes includes a reference to a key in the KSA. This key is read and 
> used to decrypt the data. When a new data node is written, an unused key is 
> selected from the KSA and used to encrypt the data node. The reference to the 
> key is then included with the node. The keys in the KSA are written before 
> actually being used to encrypt data. To securely delete a data node, we simply 
> mark the corresponding key position as deleted, and during the next purging 
> operation the KSA erase block that contains the key is then updated to a 
> version that does not contain the key.

Why do you need to have your '__u64 crypto_lookup' both in the data node
and the index? Isn't it enough to have them only inside the data nodes?
ubifs_branch anyway points to the data node and you can read your
'crypto_lookup' from there.

-- 
Best Regards,
Artem Bityutskiy

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)