7a73eedf00
They still showed UI in case of signed macros. Two decisions were made, to improve security of USE_CONFIG_APPROVE_CONFIRMATION: 1. In case of High macro security mode, valid but untrusted certificate will be automatically rejected (because it is not safe to automatically add trusted certificates) - so in this mode, USE_CONFIG_APPROVE_CONFIRMATION is the same as USE_CONFIG_REJECT_CONFIRMATION; 2. In case of Medium macro security mode, valid but untrusted certificate will not automatically allow macros execution, but will proceed to the following checks - which on Windows will try to check the source's Security Zone, and may disallow macros based on that. Only after Security Zone check the macros will be automatically allowed. Change-Id: I1a9c92c6b940b689599c5d106798ecfc691dad46 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/159214 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com> |
||
|---|---|---|
| .. | ||
| classification | ||
| doc | ||
| inc | ||
| qa | ||
| sdi | ||
| source | ||
| uiconfig/ui | ||
| util | ||
| AllLangMoTarget_sfx2.mk | ||
| CppunitTest_sfx2_classification.mk | ||
| CppunitTest_sfx2_controlleritem.mk | ||
| CppunitTest_sfx2_dialogs_test.mk | ||
| CppunitTest_sfx2_doc.mk | ||
| CppunitTest_sfx2_metadatable.mk | ||
| CppunitTest_sfx2_misc.mk | ||
| CppunitTest_sfx2_view.mk | ||
| CustomTarget_classification.mk | ||
| IwyuFilter_sfx2.yaml | ||
| JunitTest_sfx2_complex.mk | ||
| JunitTest_sfx2_unoapi.mk | ||
| Library_sfx.mk | ||
| Makefile | ||
| Module_sfx2.mk | ||
| Package_classification.mk | ||
| PythonTest_sfx2_python.mk | ||
| README.md | ||
| UIConfig_sfx.mk | ||
| UITest_sfx2_doc.mk | ||
Legacy Framework
SFX is the "old" framework, used for historical reasons.
An attempt of documentation of this module is located in [git:sfx2/doc].
It contains base classes for document model, view and controller, used
by "old" applications like sw, sc, sd (while "new" applications
are based on the "new" UNO based framework in "framework").
The SFX framework is based on dispatching slots identified by integers
(SlotIDs) to SfxShells, and there is a dedicated IDL compiler (svidl)
involved that generates C++ slot headers from SDI files in modules' sdi/
subdirectory.
Documentation about SFX dispatch, SDI etc.: https://wiki.openoffice.org/wiki/Framework/Article/Implementation_of_the_Dispatch_API_In_SFX2
Document load/save code is maintained in [git:sfx2/source/doc/docfile.cxx]
SfxMedium class, which handles all the twisty load and save corner cases.
[git:sfx2/source/appl/sfxhelp.cxx] Start procedure for the online
help viewer top level window; handling of help URL creation and
dispatch.
There are also some UNO services here that could really be implemented
anywhere, e.g. the DocumentProperties or DocumentMetadataAccess.
Notable files:
sfx2/source/dialog/backingwindow.cxx Startcenter buttons and the corresponding event handler.