[Box Backup] Danger of files being erased
boxbackup at fluffy.co.uk
Mon Feb 2 21:05:50 GMT 2004
On 2 Feb 2004, at 19:14, Eduardo Alvarenga wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Mon, 2 Feb 2004, Ben Summers wrote:
>>> If so, then all you need is a reasonable upload bandwidth
>>> limitation and an easy way of getting old versions by date and/or
>>> getting "diffs" of the live system to see what's changed, and it
>>> could be a valuable un-rootkitting tool too!
>> I think it could be as simple as having a paranoid mode where
>> 1) When you successfully connect to the server, you're then prohibited
>> from logging on again for a defined interval
> This connection means Read/Write or anything? I think Read/Write
> must be prohibited, but Read-Only no.
Yes, read only would be fine.
>> 2) Only allowing a file to be updated once per session.
> You have to thing about performance, creating 2 sockets for each file
> will be to overkilling.
Why would it create two sockets for each file?
All that would be necessary was a record of which files were touched
during the session, and only allow that to happen once.
Alternatively, only allow updates of files whose last modification time
is greater than a set time interval. This wouldn't even need any state
to be kept, as the data already exists in the store.
More information about the Boxbackup