To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92489
User mt changed the following:
What |Old value |New value
================================================================================
Target milestone|--- |OOo 3.1
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Aug 5 16:33:35 +0000
2008 -------
OOo 3.1 possible?
Lightweight solution:
If infrastructure for certificates is too complex, it would also be OK to get
some encrypted hash value from the update server, and use the known public key
to decrypt it, with some verification.
Maybe a list of different public keys, since packages are provided from
different people, who would have to encrypt the hash value with their private
key.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
