[Libreoffice-bugs] [Bug 119507] macro signature's should not be removed as long as macro source code has not changed

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=119507

Jan-Marek Glogowski <glogow at fbihome.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|https://bugs.documentfounda |
                   |tion.org/show_bug.cgi?id=10 |
                   |7882                        |
         Depends on|                            |129311

--- Comment #3 from Jan-Marek Glogowski <glogow at fbihome.de> ---
I stumbled over this while looking for a bug like 129311. So I'll just add some
update

Finished parts:
* macro signatures should not be removed as long as macro source code has not
changed => bug 42316
* prevent users to trust a signed macro with *High* macro security set and
locked trusted authors list => bug 129311

This leaves:
* signed macros should be disabled as soon as the source code has been changed
(and therefore invalidated the signature)
* user should be warned when editing signed macro code

This bug shows exactly why I don't like a single bug for multiple problems.
Maybe someone will remember to close this bug at some point, if finally all
parts are fixed, maybe not :-( More bugs will be opened eventually, if some
additional part can be / is fixed.

I also removed the bug 107882 from the "see also" list. I don't see any
connection between some Cyrillic StarBasic editor problems and this bug.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=129311
[Bug 129311] Don't ask to add a trusted macro signature, if trusted macro
signatures are read-only
-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20191210/f3f0abc6/attachment-0001.htm>