Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hello,

I've been trying to work out (1) what type of certificate you need for
signing macros and (2) how to get the option to do that. 

I've got both a document signing certificate and a code signing certificate
and, after installing them in thunderbird, they both appear for document
signing. For macros, however, I can't seem to make the macros > digital
signatures option enable. 

I've enabled experimental features, which gave me macro recording, and threw
in a hello world macro to make sure there was something to sign but digital
signatures are still greyed out.

I'm sure there's an answer but lots of googling and both irc channels
haven't provided one. Can anybody on the list help?

Currently running Version 4.0.4.2 (Build ID: 4.0.4.2-9.el6) on CentOS. Any
help would be much appreciated



--
View this message in context: 
http://nabble.documentfoundation.org/Digital-signatures-for-macros-tp4091610.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.