Il mer 10 ott 2018, 23:34 Norman Dunbar via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:
> Hi Giorgio,
>
> but the applications can change any part of the header, especially if the
> user has DJToolkit, Turbo Toolkit, TK2 etc. So should we stop using file
> lengths, data space, file types
Hi Giorgio,
but the applications can change any part of the header, especially if the user
has DJToolkit, Turbo Toolkit, TK2 etc. So should we stop using file lengths,
data space, file types etc?
Not once has my own backup system been compimised by any application writing to
the header, nor
IMHO it's too vulnerable, anyone can change that.
It would be much safer to store it in an internal application database.
It is the concept itself that an application can directly modify file
system data that is dangerous.
Giorgio
Giorgio,
nothing dangerous here. DEC VMS, for example, does it in exactly in the same
way.
The danger you seem to see (application sets a backup date, other app uses
something different) is circumvented by supplying an old "full" backup to any
incremental one for the programs to compare. In
