To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92940
User ab changed the following:
What |Old value |New value
================================================================================
Priority|P3 |P2
--------------------------------------------------------------------------------
Target milestone|OOo 3.1 |OOo 3.0
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Sep 9 13:12:59 +0000
2008 -------
If the shared code stored on a device where the user has no write access,
it's not possible to commit any changes anyway. So I see no real security
issue here, but I agree that setting shared extension libs to read only
would be better.
But: As notified by a user on the extensions dev mailing list this problem
also applies to user extensions. They can be edited but saving the changes
does not succeed. This is a regression and as discussed with mh it will
be fixed as 3.0 showstopper in the scope of this issue.
Additionally libraries in shared extensions will be made read only like all
pre installed shared libraries.
-> OOo 3.0, P2 (data loss)
---------------------------------------------------------------------
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]
