Justin Fitzgibbon wrote:

> This security should be on two levels - lower which allows


changes on entering a password and locked _which prevents changes ever being made.



If the contents of a document can be decrypted in order to view it theres no way to then lock it against changes, or prevent people printing it etc, using open source code.

However it should be relatively easy to automatically compare signed
documents
(storing the signatures in a database) with newly opened documents, and
pop up a message, eg "this document was signed by you on dd/mm/yyyy, and is
a valid copy" if you didn't get such a message you would know the document had been
tampered with.


You could even have corporate signature database eg this document was
signed by your boss, coworker etc.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





The idea of a database of digital signatures could be really useful - I have often wondered about the idea of identifying operators and assigning a dedicated font to them so that their work would be easy to identify - perhaps not a great idea in our modern free society but with more than one person working on projects becoming so common it could make managing projects much more transparent. Although speadsheets have been a great tool for accountants and auditors their ease of manipulation in shared data situations is becoing a very real problem.

I am greatful for the keen interest shown - I really did not expect such interest when I joined the group.


Jeremy

Reply via email to