From ad327e4ae85f2bd79b17a79fe050196beef31298 Mon Sep 17 00:00:00 2001 From: Ivo Hinkelmann Date: Thu, 17 Sep 2009 13:53:54 +0000 Subject: CWS-TOOLING: integrate CWS encsig09 2009-09-14 15:11:29 +0200 oc r276125 : #i105049# MacroSignatur needs Macro 2009-09-09 17:09:46 +0200 jl r276005 : #i103989# could not signe encrypted doc containing a formular object 2009-09-09 13:11:24 +0200 jl r275985 : #i103989# could not signe encrypted doc containing a formular object 2009-09-08 15:54:02 +0200 mav r275934 : #i103906# fix the automation test scenario ( tempfile should be writable for the user ) 2009-09-07 14:01:39 +0200 mav r275895 : #i103906# fix the problem with reload 2009-09-07 09:34:48 +0200 mav r275871 : #i104786# do the ODF version check only for ODF documents 2009-09-07 08:19:06 +0200 mav r275870 : #i104389# fix text 2009-09-06 22:24:21 +0200 mav r275867 : #i104786# check the consistency of ODF version 2009-09-06 22:23:24 +0200 mav r275866 : #i104786# check the consistency of ODF version 2009-09-06 22:23:00 +0200 mav r275865 : #i104786# check the consistency of ODF version 2009-09-06 22:22:36 +0200 mav r275864 : #i104786# check the consistency of ODF version 2009-09-06 22:22:03 +0200 mav r275863 : #i104786# check the consistency of ODF version 2009-09-02 17:09:30 +0200 mav r275722 : #i104715# let repairing mechanics use the streams correctly 2009-09-01 16:52:49 +0200 mav r275670 : #i104389# notify user not to trust the corrupted document 2009-09-01 16:31:37 +0200 mav r275668 : #i104389# use vnd.sun.star.zip: protocol to access zip files 2009-09-01 16:30:32 +0200 mav r275667 : #i104389# use vnd.sun.star.zip: protocol to access zip files 2009-09-01 16:22:13 +0200 jl r275666 : #i104339# small content change 2009-09-01 14:20:42 +0200 jl r275660 : #i103519# remove some debug output 2009-09-01 13:51:52 +0200 jl r275659 : #i103519# NSS uses '\' for escaping in distinguished names 2009-09-01 12:49:47 +0200 mav r275655 : #i104389# use zip-mode to read from jar files 2009-09-01 12:40:22 +0200 mav r275653 : #i104389# use zip-mode to read from jar files 2009-09-01 12:32:29 +0200 mav r275652 : #i104389# use constants 2009-08-31 21:58:00 +0200 mav r275637 : #i10000# fix warning 2009-08-31 21:11:17 +0200 mav r275636 : #i104227# adding of scripting signature removes the document signature 2009-08-31 20:55:05 +0200 mav r275635 : #i103905# ZipStorage supports Compressed property 2009-08-31 20:53:55 +0200 mav r275634 : #i103905# adjust macro signature transfer to usage of ZipStorage 2009-08-31 15:30:49 +0200 jl r275609 : #i103989# warning is shown as long the user does not click 'OK' 2009-08-31 14:36:10 +0200 jl r275608 : #i103989# changed warning text when signing macro and there is a document signature. This warning is only displayed once 2009-08-31 13:34:41 +0200 mav r275603 : #i104452# disable macros in repaired documents 2009-08-31 13:33:42 +0200 mav r275602 : #i104452# disable macros in repaired documents 2009-08-31 13:03:56 +0200 jl r275600 : #i45212# signature dialog could not be started when using read-only documents 2009-08-31 09:26:13 +0200 mav r275583 : #i104578# store the additional entry as the last one to workaround parsing problem in OOo3.1 and later 2009-08-30 20:54:25 +0200 mav r275562 : #i10000# adopt for unix 2009-08-30 10:56:00 +0200 mav r275561 : CWS-TOOLING: rebase CWS encsig09 to trunk@275331 (milestone: DEV300:m56) 2009-08-28 16:34:00 +0200 mav r275539 : #i104578# write necessary info in manifest.xml for ODF1.2 encrypted document 2009-08-28 14:04:22 +0200 mav r275533 : #104587# fix handling of readonly streams 2009-08-28 13:58:10 +0200 mav r275531 : #i104389# fix the broken document handling 2009-08-28 11:40:39 +0200 mav r275522 : #i104389# fix the signature streams check 2009-08-27 21:48:12 +0200 mav r275509 : #i103927# show the warning 2009-08-27 21:47:48 +0200 mav r275508 : #i103927# show the warning 2009-08-27 16:45:59 +0200 jl r275495 : #i45212# remove unused variable 2009-08-27 16:34:00 +0200 jl r275494 : #i103989# 2009-08-27 13:54:28 +0200 jl r275482 : #i103519# fixed replacement of 'S' by 'ST' 2009-08-27 12:32:21 +0200 mav r275472 : #i10000# fix warning 2009-08-27 11:58:11 +0200 mav r275467 : #i104389# handle the entry path correctly 2009-08-26 17:18:35 +0200 jl r275438 : #i103519# subject and issuer distinguished names were not properly displayed. The strings were obtained by system functions (Windows, NSS), which use quotes to escape the values, when they contain special characters 2009-08-26 11:00:20 +0200 mav r275403 : #i10000# fix warnings 2009-08-26 08:25:45 +0200 mav r275392 : #i10000# fix warning 2009-08-26 08:02:22 +0200 mav r275391 : #i10000# adopt for linux 2009-08-26 07:40:30 +0200 mav r275390 : #i10000# fix warning 2009-08-26 07:35:28 +0200 mav r275389 : #i10000# use correct include file name 2009-08-25 15:01:41 +0200 jl r275356 : #i103989# better check for mimetype of streams 2009-08-25 09:07:09 +0200 mav r275335 : CWS-TOOLING: rebase CWS encsig09 to trunk@274622 (milestone: DEV300:m54) 2009-08-24 18:17:02 +0200 mav r275329 : #i103927# check the nonencrypted streams 2009-08-24 18:14:14 +0200 mav r275328 : #i103927# check the nonencrypted streams 2009-08-24 17:59:34 +0200 mav r275327 : #i103927#,#i104389# check the package consistency and nonencrypted streams 2009-08-24 16:18:28 +0200 jl r275323 : #i103989# added comment 2009-08-24 13:08:47 +0200 jl r275305 : #i45212# #i66276# only write the X509Certificate element once and allow to add remove several certificates at a time 2009-08-21 12:57:28 +0200 ufi r275239 : 104339 2009-08-21 08:39:05 +0200 jl r275213 : #i10398# comparing URIs of signed files with the 'element list' 2009-08-20 13:39:47 +0200 jl r275178 : #i10398# displaying 'new partially signed' status in the status bar 2009-08-20 13:35:39 +0200 jl r275177 : #i10398# displaying 'new partially signed' status in the status bar 2009-08-20 13:29:06 +0200 jl r275176 : #i10398# displaying 'new partially signed' status in the status bar 2009-08-20 13:26:21 +0200 jl r275175 : #i10398# displaying 'new partially signed' status in the status bar 2009-08-20 12:05:09 +0200 ufi r275170 : i104339 2009-08-19 12:24:54 +0200 jl r275146 : #i10398# displaying 'old signature' icon and status in signature dialog 2009-08-18 15:18:48 +0200 jl r275111 : #i103989# document signatures containing manifest.xml are now validated according to the final ODF1.2 spec 2009-08-18 11:41:06 +0200 mav r275087 : #i103927# detect if encrypted ODF1.2 document contains nonencrypted streams 2009-08-18 11:35:13 +0200 mav r275085 : #i103927# detect if encrypted ODF1.2 document contains nonencrypted streams 2009-08-14 17:32:41 +0200 jl r274999 : #i103989# using c14n tranformation for XML streams 2009-08-14 15:27:43 +0200 jl r274987 : #i103989# remove special handling for encrypted document streams in UriBindingHelper::OpenInputStream, since we use zip storage this is not necessary anymore 2009-08-14 15:08:10 +0200 jl r274983 : #i103989# Showing a message when adding or removing a macro signature, that the document signature will be removed 2009-08-14 14:57:27 +0200 jl r274982 : #i103989# accesing Sequence at invalid index 2009-08-11 08:55:02 +0200 mav r274846 : #i103905# let signing service know if there is already a valid document signature 2009-08-10 11:33:37 +0200 jl r274799 : #i103905# do not truncate the stream 2009-08-10 10:43:47 +0200 mav r274797 : #i103905# provide the storage version 2009-08-07 16:58:46 +0200 jl r274780 : #i103989# 2009-08-07 16:56:19 +0200 jl r274779 : #i103989# using odf version string etc. 2009-08-07 15:20:53 +0200 mav r274771 : #i103905# provide the storage version 2009-08-07 15:19:12 +0200 mav r274770 : #i103905# provide the storage version 2009-08-07 12:41:45 +0200 mav r274758 : #103930# do not store thumbnail in case of encrypted document 2009-08-07 12:36:52 +0200 mav r274757 : #i103905# provide the storage version 2009-08-07 12:15:54 +0200 mav r274754 : #i103760# the signed state is not lost on saving 2009-08-07 12:06:19 +0200 mav r274753 : #i103760# avoid warning regarding signature removal on export 2009-08-07 12:06:01 +0200 mav r274752 : #i103760# avoid warning regarding signature removal on export 2009-08-06 08:47:34 +0200 mav r274703 : #i103905# allow to transport ODF version to the signing component 2009-08-05 21:34:42 +0200 mav r274701 : #i103905# allow to transport ODF version to the signing component 2009-08-05 15:48:17 +0200 mav r274683 : #i103905# allow to transport ODF version to the signing component 2009-08-05 14:58:12 +0200 jl r274673 : #i103989# documentsignature now signes all streams except documentsignatures.xml, all streams are processed as binary files 2009-08-05 12:00:32 +0200 mav r274648 : #i103905# allow to transport ODF version to the signing component 2009-08-04 10:57:04 +0200 jl r274612 : #i103989# added XInitialization 2009-07-31 10:32:27 +0200 mav r274516 : #i103905# use zip storage to sign documents 2009-07-30 14:01:33 +0200 mav r274489 : #i103906# optimize the usage of temporary medium 2009-07-30 14:00:28 +0200 mav r274488 : #i103906# optimize the usage of temporary medium 2009-07-30 13:59:09 +0200 mav r274487 : #i103906# optimize the usage of temporary medium 2009-07-30 13:50:44 +0200 mav r274485 : #i103906# optimize the usage of temporary medium 2009-07-30 13:49:53 +0200 mav r274484 : #i103906# optimize the usage of temporary medium 2009-07-30 13:49:13 +0200 mav r274483 : #i103906# optimize the usage of temporary medium 2009-07-30 13:47:09 +0200 mav r274482 : #i103905#,#i103906# let the signing process use zip-storage; optimize the usage of temporary medium 2009-07-21 09:10:31 +0200 mav r274159 : CWS-TOOLING: rebase CWS encsig09 to trunk@273468 (milestone: DEV300:m51) 2009-05-05 08:39:01 +0200 mav r271496 : #i100832# allow to sign macros only when there are any --- .../source/text/shared/01/digitalsignatures.xhp | 76 +++++---- .../text/shared/guide/digital_signatures.xhp | 116 ++++++++++---- .../source/text/shared/guide/digitalsign_send.xhp | 178 +++++++++------------ 3 files changed, 196 insertions(+), 174 deletions(-) (limited to 'helpcontent2/source/text/shared') diff --git a/helpcontent2/source/text/shared/01/digitalsignatures.xhp b/helpcontent2/source/text/shared/01/digitalsignatures.xhp index d9fe1d5bb0..39979a49e5 100644 --- a/helpcontent2/source/text/shared/01/digitalsignatures.xhp +++ b/helpcontent2/source/text/shared/01/digitalsignatures.xhp @@ -1,8 +1,8 @@ - - + + + - - -Digital Signatures -/text/shared/01/digitalsignatures.xhp - - -UFI: Digital Signatures from File-Properties-General -dedr: reviewed - - - -
+ + Digital Signatures + /text/shared/01/digitalsignatures.xhp + + + +
-Digital Signatures -Adds and removes digital signatures to and from your document. You can also use the dialog to view certificates. -
-
- -
- +Digital Signatures + Adds and removes digital signatures to and from your document. You can also use the dialog to view certificates. +
+
+ +
+ -You must save a file before you can apply a digital signature to the file. +You must save a file before you can apply a digital signature to the file. -You must save a file in OpenDocument format before you can apply a digital signature to the file. +You must save a file in OpenDocument format before you can apply a digital signature to the file. -List -Lists the digital signatures for the current document. -The Signed icon -icon +List + Lists the digital signatures for the current document. + The Signed icon +Icon indicates a valid digital signature, while the Exclamation mark icon -icon +Icon indicates an invalid digital signature. -A Signed icon is also shown in the Status bar when a signed document only contains valid digital signatures. + See also Digital Signatures. -View Certificate -Opens the View Certificate dialog. +View Certificate + Opens the View Certificate dialog. -Add -Opens the Select Certificate dialog. +Add + Opens the Select Certificate dialog. -Remove -Removes the selected source from the list. - - +Remove + Removes the selected source from the list. + + \ No newline at end of file diff --git a/helpcontent2/source/text/shared/guide/digital_signatures.xhp b/helpcontent2/source/text/shared/guide/digital_signatures.xhp index f1369473ab..f7d56606a1 100755 --- a/helpcontent2/source/text/shared/guide/digital_signatures.xhp +++ b/helpcontent2/source/text/shared/guide/digital_signatures.xhp @@ -10,8 +10,8 @@ * * OpenOffice.org - a multi-platform office productivity suite * - * $RCSfile: digital_signatures.xhp,v $ - * $Revision: 1.14.4.1 $ + * $RCSfile: soffice2xmlhelp.xsl,v $ + * $Revision: 1.8 $ * * This file is part of OpenOffice.org. * @@ -35,38 +35,86 @@ - -About Digital Signatures -/text/shared/guide/digital_signatures.xhp - - - + + About Digital Signatures + /text/shared/guide/digital_signatures.xhp + + + certificates -digital signatures;overview -security;digital signatures + digital signatures;overview + security;digital signatures mw moved 1 entry to digitalsign_send.xhp and made "digital signatures" a two level entry and added a new entry -About Digital Signatures +About Digital Signatures -In %PRODUCTNAME, you can digitally sign your documents and macros. -Certificates -To sign a document digitally, you need a personal key, the certificate. A personal key is stored on your computer as a combination of a private key, which must be kept secret, and a public key, which you add to your documents when you sign them. -Save and sign the document -When you apply a digital signature to a document, a kind of checksum is computed from the document's content plus your personal key. The checksum and your public key are stored together with the document. -Open a signed document -When someone later opens the document on any computer with a recent version of %PRODUCTNAME, the program will compute the checksum again and compare it with the stored checksum. If both are the same, the program will signal that you see the original, unchanged document. In addition, the program can show you the public key information from the certificate. -You can compare the public key with the public key that is published on the web site of the certificate authority. -Whenever someone changes something in the document, this change breaks the digital signature. After the change, there will be no sign that you see the original document. -Security Warnings -When you receive a signed document, and the software reports that the signature is valid, this does not mean that you can be absolutely sure that the document is the same that the sender has sent. Signing documents with software certificates is not a perfectly secure method. Numerous ways are possible to circumvent the security features. -Example: Think about someone who wants to camouflage his identity to be a sender from your bank. He can easily get a certificate using a false name, then send you any signed e-mail pretending he is working for your bank. You will get that e-mail, and the e-mail or the document within has the "valid signed" icon. -Do not trust the icon. Inspect and verify the certificates. -The validation of a signature is not a legally binding guarantee of any kind. -On Windows operating systems, the Windows features of validating a signature are used. On Solaris and Linux systems, files that are supplied by Thunderbird, Mozilla or Firefox are used. You must ensure that the files that are in use within your system are really the original files that were supplied by the original developers. For malevolent intruders, there are numerous ways to replace original files with other files that they supply. -The messages about validation of a signature that you see in %PRODUCTNAME are the messages that the validation files return. The %PRODUCTNAME software has no way to ensure that the messages reflect the true status of any certificate. The %PRODUCTNAME software only displays the messages that other files that are not under control of %PRODUCTNAME report. There is no legal responsibility of %PRODUCTNAME that the displayed messages reflect the true status of a digital signature. -
-English Wiki page on digital signatures -Applying digital signatures -Opening a document using WebDAV over HTTPS -
- - + In %PRODUCTNAME, you can digitally sign your documents and macros. + Certificates + To sign a document digitally, you need a personal key, the certificate. A personal key is stored on your computer as a combination of a private key, which must be kept secret, and a public key, which you add to your documents when you sign them. + Save and sign the document + When you apply a digital signature to a document, a kind of checksum is computed from the document's content plus your personal key. The checksum and your public key are stored together with the document. + Open a signed document + When someone later opens the document on any computer with a recent version of %PRODUCTNAME, the program will compute the checksum again and compare it with the stored checksum. If both are the same, the program will signal that you see the original, unchanged document. In addition, the program can show you the public key information from the certificate. + You can compare the public key with the public key that is published on the web site of the certificate authority. + Whenever someone changes something in the document, this change breaks the digital signature. After the change, there will be no sign that you see the original document. + The result of the signature validation is displayed in the status bar and within the Digital Signature dialog. Several documents and macro signatures can exist inside an ODF document. If there is a problem with one signature, then the validation result of that one signature is assumed for all signatures. That is, if there are ten valid signatures and one invalid signature, then the status bar and the status field in the dialog will flag the signature as invalid. + You can see any of the following icons and messages when you open a signed document. + + + + Icon in Status bar + + + Signature status + + + + + +Icon + + + + The signature is valid. + + + + + +Icon + + + + The signature is OK, but the certificates could not be validated. + The signature and the certificate are OK, but not all parts of the document are signed. (For documents that were signed with OpenOffice.org prior to 3.2 or StarOffice prior to 9.2, see note below.) + + + + + +Icon + + + + The signature is invalid. + + +
+ + Signatures and software versions + The signing of contents got changed with OpenOffice.org 3.2 and StarOffice 9.2. Now all contents of the files, except the signature file itself (META-INF/documentsignatures.xml) are signed. + When you sign a document with OpenOffice.org 3.2 or StarOffice 9.2 or a later version, and you open that document in an older version of the software, the signature will be displayed as "invalid". Signatures created with older versions of the software will be marked with "only parts of the documents are signed" when loaded in the newer software. + When you load an ODF document, you might see an icon in the status bar and the status field in the dialog that indicates that the document is only partially signed. This status will appear when the signature and certificate are valid, but they were created with a version of OpenOffice.org before 3.2 or StarOffice before 9.2. In versions of OpenOffice.org before 3.0 or StarOffice before 9.0, the document signature was applied to the main contents, pictures and embedded objects only and some contents, like macros, were not signed. In OpenOffice.org 3.0 and StarOffice 9.0 the document signature was applied to most content, including macros. However, the mimetype and the content of the META-INF folder were not signed. And in OpenOffice.org 3.2 and StarOffice 9.2 all contents, except the signature file itself (META-INF/documentsignatures.xml), are signed. + Security Warnings + When you receive a signed document, and the software reports that the signature is valid, this does not mean that you can be absolutely sure that the document is the same that the sender has sent. Signing documents with software certificates is not a perfectly secure method. Numerous ways are possible to circumvent the security features. + Example: Think about someone who wants to camouflage his identity to be a sender from your bank. He can easily get a certificate using a false name, then send you any signed e-mail pretending he is working for your bank. You will get that e-mail, and the e-mail or the document within has the "valid signed" icon. + Do not trust the icon. Inspect and verify the certificates. + The validation of a signature is not a legally binding guarantee of any kind. + On Windows operating systems, the Windows features of validating a signature are used. On Solaris and Linux systems, files that are supplied by Thunderbird, Mozilla or Firefox are used. You must ensure that the files that are in use within your system are really the original files that were supplied by the original developers. For malevolent intruders, there are numerous ways to replace original files with other files that they supply. + The messages about validation of a signature that you see in %PRODUCTNAME are the messages that the validation files return. The %PRODUCTNAME software has no way to ensure that the messages reflect the true status of any certificate. The %PRODUCTNAME software only displays the messages that other files that are not under control of %PRODUCTNAME report. There is no legal responsibility of %PRODUCTNAME that the displayed messages reflect the true status of a digital signature. +
+ English Wiki page on digital signatures + Applying digital signatures + Opening a document using WebDAV over HTTPS +
+ + \ No newline at end of file diff --git a/helpcontent2/source/text/shared/guide/digitalsign_send.xhp b/helpcontent2/source/text/shared/guide/digitalsign_send.xhp index 774e0f4069..b68bb1240f 100644 --- a/helpcontent2/source/text/shared/guide/digitalsign_send.xhp +++ b/helpcontent2/source/text/shared/guide/digitalsign_send.xhp @@ -1,9 +1,8 @@ - - - + + - - - + + - -Applying Digital Signatures -/text/shared/guide/digitalsign_send.xhp - - - - - - + + Applying Digital Signatures + /text/shared/guide/digitalsign_send.xhp + + + signing documents with digital signatures -digital signatures;getting/managing/applying - - mw transferred one entry from digital_signatures.xhp and added a new entry - Applying Digital Signatures - - MW created this file by splitting shared/guide/digital_signatures.xhp - Getting a Certificate - You can get a certificate from a certification authority, which may be a private company or a governmental institution. Some certification authorities want money for their service, for example when they certify your identity. Other certificates are free of costs, for example those offered by some e-mail providers, which certify your e-mail address. A few of the companies that offer certificates to private persons are listed in the following, in alphabetical order: GlobalSign , Thawte, Verisign. - Managing your Certificates - + digital signatures;getting/managing/applying +mw transferred one entry from digital_signatures.xhp and added a new entry +Applying Digital Signatures +MW created this file by splitting shared/guide/digital_signatures.xhp +Getting a Certificate + You can get a certificate from a certification authority, which may be a private company or a governmental institution. Some certification authorities want money for their service, for example when they certify your identity. Other certificates are free of costs, for example those offered by some e-mail providers, which certify your e-mail address. A few of the companies that offer certificates to private persons are listed in the following, in alphabetical order: GlobalSign , Thawte, Verisign. + Managing your Certificates - - If you are using Microsoft Windows, you can manage your certificates from the Control Panel applet "Internet Options" on the "Contents" tab page. - Import your new root certificate into the Trusted Root Certification Authorities list. - +If you are using Microsoft Windows, you can manage your certificates from the Control Panel applet "Internet Options" on the "Contents" tab page. + Import your new root certificate into the Trusted Root Certification Authorities list. - - If you are using Solaris or Linux, you must install a recent version of Thunderbird, Mozilla Suite, or Firefox software to install some system files that are needed for encryption. - If you have created different profiles in Thunderbird, Mozilla, or Firefox, and you want %PRODUCTNAME to use one specified profile for certificates, then you can set the environment variable MOZILLA_CERTIFICATE_FOLDER to point to the folder of that specified profile. - - - Open your Web browser's preferences dialog, select the Privacy & Security tab page, click on Certificates - Manage Certificates. - - - Import your new root certificate, then select and edit the certificate. Enable the root certificate to be trusted at least for web and email access. This ensures that the certificate can sign your documents. You may edit any intermediate certificate in the same way, but it is not mandatory for signing documents. - - - When you have edited the new certificates, restart %PRODUCTNAME. - - - +If you are using Solaris or Linux, you must install a recent version of Thunderbird, Mozilla Suite, or Firefox software to install some system files that are needed for encryption.how about Mac OS X? + If you have created different profiles in Thunderbird, Mozilla, or Firefox, and you want %PRODUCTNAME to use one specified profile for certificates, then you can set the environment variable MOZILLA_CERTIFICATE_FOLDER to point to the folder of that specified profile. + + + Open your Web browser's preferences dialog, select the Privacy & Security tab page, click on Certificates - Manage Certificates. + + + Import your new root certificate, then select and edit the certificate. Enable the root certificate to be trusted at least for web and email access. This ensures that the certificate can sign your documents. You may edit any intermediate certificate in the same way, but it is not mandatory for signing documents. + + + When you have edited the new certificates, restart %PRODUCTNAME. + + - - Signing a document - - - Choose File - Digital Signatures. - - - A message box advises you to save the document. Click Yes to save the file. - - - After saving, you see the Digital Signatures dialog. Click Add to add a public key to the document. - - - In the Select Certificate dialog, select your certificate and click OK. - - - You see again the Digital Signatures dialog, where you can add more certificates if you want. Click OK to add the public key to the saved file. - - - A signed document shows an icon -icon +Signing a document + + + Choose File - Digital Signatures. + + + A message box advises you to save the document. Click Yes to save the file. + + + After saving, you see the Digital Signatures dialog. Click Add to add a public key to the document. + + + In the Select Certificate dialog, select your certificate and click OK. + + + You see again the Digital Signatures dialog, where you can add more certificates if you want. Click OK to add the public key to the saved file. + + + A signed document shows an icon +Icon in the status bar. You can double-click the icon in the status bar to view the certificate. - Signing the macros inside a document - Normally, macros are part of a document. If you sign a document, the macros inside the document are signed automatically. If you want to sign only the macros, but not the document, proceed as follows: - - - Choose Tools - Macros - Digital Signature. - - - Apply the signature as described above for documents. - - - When you open the Basic IDE that contains signed macros, you see an icon -icon - in the status bar. You can double-click the icon in the status bar to view the certificate. - WebDAV see issue 32935 - main dialog IDs are here to lead the user initially to this help page - Examine certificate button - + The result of the signature validation is displayed in the status bar and within the Digital Signature dialog. Several documents and macro signatures can exist inside an ODF document. If there is a problem with one signature, then the validation result of that one signature is assumed for all signatures. That is, if there are ten valid signatures and one invalid signature, then the status bar and the status field in the dialog will flag the signature as invalid. + Signing the macros inside a document + Normally, macros are part of a document. If you sign a document, the macros inside the document are signed automatically. If you want to sign only the macros, but not the document, proceed as follows: + + + Choose Tools - Macros - Digital Signature. + + + Apply the signature as described above for documents. + + + When you open the Basic IDE that contains signed macros, you see an icon +Icon + in the status bar. You can double-click the icon in the status bar to view the certificate.WebDAV see issue 32935main dialog IDs are here to lead the user initially to this help pageExamine certificate button - Click to open the View Certificate dialog. - Accept this certificate temporarily for this session radio button - +Click to open the View Certificate dialog.Accept this certificate temporarily for this session radio button - Choose this setting to accept the certificate until you exit %PRODUCTNAME. - Do not accept this certificate and do not connect to this Web site radio button - +Choose this setting to accept the certificate until you exit %PRODUCTNAME.Do not accept this certificate and do not connect to this Web site radio button - Choose this setting to cancel the connection. -
- - English Wiki page on digital signatures - About digital signatures - -
- - +Choose this setting to cancel the connection. +
+ English Wiki page on digital signatures + About digital signatures +
+ + \ No newline at end of file -- cgit