Valentina 2.0. -- What is your 3 DREAM features? // db.EraseOnDelete

[Ruslan Zasukhin]

on 1/31/04 11:48 PM, Robert Brenstein at rjb at rz.uni-potsdam.de wrote:

>>>  For encrypted it should be done by default, opposite than for
>>>  unencrypted. We discussed this last year. If it is not done, there is
>>>  a chance of inappropriate data exposure to prying eyes.
>> 
>> But data are encrypted!
>> 
>> What problems?
>> 
>> Nobody can read them. Garbage.
>> 
>> If you think that somebody can read encrypted data,
>> Then your original encrypted data even in more danger.
>> 
>> Hopefully, encrypted data are protected.
> 
> As far as I know, Valentian encrypts only current data. Since data
> may be left in records deleted before encryption that data may remain
> visible. Or does valentina encrypt now all records, regardless
> whether they are deleted or not?

I see what you mean.

   records DELETED before ENCRYPTION set.

Mmmm,

Valentina always encrypt 1KB of data, one by one.
So it do not choose between deleted and existed records.

In 2.0, files always will be read by 4KB pages.
And encrypted will be page a block.

So no problems I think.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------