On Fri, 2012-05-11 at 13:24 +0200, Joel Reardon wrote:
> This patch adds a new field to the TNC's zbranch and allows it to be set when
> a node is added or replaced. The field is called 'crypto_lookup' and it refers
> to a location in the key storage area---a pointer to a key that is used to
> encrypt/decrypt the data node. It can be set to 0 or a negative number when it
> is not being used. When a new node is added, this value is passed and set
> When a node is replace, the old value is replaced with the new value.
> 
> These values will be used in future patchs. Replacing a
> crypto_lookup value will also mark the old value as deleted and the new value
> as used; adding a new node will mark the value as used. Additionally, deleting
> or removing TNC nodes will mark the values as deleted.
> 
> TNC's crypto_lookup values are not stored on disk. They will be stored in the
> data
> node's header. Therefore, if a crypto_lookup value is invalid (but a valid one
> is to be expected and needs to be used) then a function will be added that
> reads the data node to
> obtain the value. Additionally, when a data node is ever read, the
> crypto_lookup position that is read will be set in the corresponding zbranch.
> 
> The values are not stored on disk to avoid having different on-disk formats of
> the the ubifs_branch structure.
> 
> Signed-off-by: Joel Reardon <reardonj@inf.ethz.ch>

Pushed to the "joel" branch, thanks!

-- 
Best Regards,
Artem Bityutskiy