source/text/shared/guide/digital_signatures.xhp | 22 +++++++++++-----------
source/text/shared/guide/openpgp.xhp | 2 +-
2 files changed, 12 insertions(+), 12 deletions(-)
New commits:
commit 042260679dc7ffb1babd88e129662d1c6419cb12
Author: Olivier Hallot <olivier.hal...@libreoffice.org>
AuthorDate: Tue Dec 31 10:22:11 2019 -0300
Commit: Olivier Hallot <olivier.hal...@libreoffice.org>
CommitDate: Tue Dec 31 22:22:04 2019 +0100
Fix broken link
Change-Id: Iad45d159e70142f458fbe185aa1f659902924de4
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/86044
Tested-by: Jenkins
Reviewed-by: Olivier Hallot <olivier.hal...@libreoffice.org>
diff --git a/source/text/shared/guide/digital_signatures.xhp
b/source/text/shared/guide/digital_signatures.xhp
index 84ff4cfea..188cd8c14 100644
--- a/source/text/shared/guide/digital_signatures.xhp
+++ b/source/text/shared/guide/digital_signatures.xhp
@@ -30,14 +30,14 @@
<bookmark_value>digital signatures;overview</bookmark_value>
<bookmark_value>security;digital signatures</bookmark_value>
</bookmark><comment>mw moved 1 entry to digitalsign_send.xhp and made "digital
signatures" a two level entry and added a new entry</comment>
-<paragraph xml-lang="en-US" id="hd_id2767418" role="heading"
level="1"><variable id="digital_signatures"><link
href="text/shared/guide/digital_signatures.xhp">About Digital Signatures</link>
-</variable></paragraph>
+<h1 id="hd_id2767418"><variable id="digital_signatures"><link
href="text/shared/guide/digital_signatures.xhp">About Digital Signatures</link>
+</variable></h1>
<paragraph xml-lang="en-US" id="par_idN10632" role="paragraph">In
%PRODUCTNAME, you can digitally sign your documents and macros. </paragraph>
- <paragraph xml-lang="en-US" id="hd_id6564531" role="heading"
level="2">Certificates</paragraph>
+ <h2 id="hd_id6564531">Certificates</h2>
<paragraph xml-lang="en-US" id="par_idN10639" role="paragraph">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.</paragraph>
- <paragraph xml-lang="en-US" id="par_idN1066D" role="heading"
level="2">Save and sign the document</paragraph>
+ <h2 id="par_idN1066D">Save and sign the document</h2>
<paragraph xml-lang="en-US" id="par_idN10671" role="paragraph">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.</paragraph>
- <paragraph xml-lang="en-US" id="par_idN10674" role="heading"
level="2">Open a signed document</paragraph>
+ <h2 id="par_idN10674">Open a signed document</h2>
<paragraph xml-lang="en-US" id="par_idN10678" role="paragraph">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.</paragraph>
<paragraph xml-lang="en-US" id="par_idN1067B" role="paragraph">You can
compare the public key with the public key that is published on the web site of
the certificate authority.</paragraph>
<paragraph xml-lang="en-US" id="par_idN1067E" role="paragraph">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.</paragraph>
@@ -85,22 +85,22 @@
</tablerow>
</table>
- <paragraph xml-lang="en-US" id="hd_id0821200910191787" role="heading"
level="3">Signatures and software versions</paragraph>
+ <h3 id="hd_id0821200910191787">Signatures and software versions</h3>
<paragraph xml-lang="en-US" id="par_id0821200910191747"
role="paragraph">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. </paragraph>
<paragraph xml-lang="en-US" id="par_id0821200910191774"
role="paragraph">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 document
are signed" when loaded in the newer software.</paragraph>
<paragraph xml-lang="en-US" id="par_id0821200910191775"
role="paragraph">When you sign an OOXML document, then the signature will be
always marked with "only parts of the document are signed". Metadata of OOXML
files are never signed, to be compatible with Microsoft Office.</paragraph>
<paragraph xml-lang="en-US" id="par_id0821200910191776"
role="paragraph">When you sign a PDF document, then this marking is not used.
Signing only parts of the document is simply an invalid signature.</paragraph>
<paragraph xml-lang="en-US" id="par_id0821200910191777"
role="paragraph">Signing other document formats is not supported at the
moment.</paragraph>
- <paragraph xml-lang="en-US" id="par_id2008200911583098" role="note">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, StarOffice 9.2, and all versions of
LibreOffice all contents, except the signature file itself
(META-INF/documentsignatures.xml), are signed.</paragraph>
- <paragraph xml-lang="en-US" id="hd_id9354228" role="heading"
level="2">Security Warnings</paragraph>
+ <note id="par_id2008200911583098">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, StarOffice 9.2, and all versions of LibreOffice all
contents, except the signature file itself (META-INF/documentsignatures.xml),
are signed.</note>
+ <h2 id="hd_id9354228">Security Warnings</h2>
<paragraph xml-lang="en-US" id="par_id2372508" role="paragraph">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.</paragraph>
<paragraph xml-lang="en-US" id="par_id7953123" role="paragraph">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.
</paragraph>
<paragraph xml-lang="en-US" id="par_id6195257" role="paragraph">Do not
trust the icon. Inspect and verify the certificates.</paragraph>
- <paragraph xml-lang="en-US" id="par_id8635517" role="warning">The
validation of a signature is not a legally binding guarantee of any
kind.</paragraph>
+ <warning id="par_id8635517">The validation of a signature is not a
legally binding guarantee of any kind.</warning>
<paragraph xml-lang="en-US" id="par_id6075624" role="paragraph">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.</paragraph>
- <paragraph xml-lang="en-US" id="par_id6819971" role="warning">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.</paragraph>
+ <warning id="par_id6819971">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.</warning>
<section id="relatedtopics">
- <paragraph role="paragraph" id="par_id681543699425744"
localize="false"><embedvar href="text/shared/guide/openpgp.xhp#openpgphead"
markup="ignore"/></paragraph>
+ <paragraph role="paragraph" id="par_id681543699425744"
localize="false"><embedvar href="text/shared/guide/openpgp.xhp#openpgph1"
markup="ignore"/></paragraph>
<paragraph xml-lang="en-US" id="par_id3204443" role="paragraph"><link
href="https://wiki.documentfoundation.org/How_to_use_digital_Signatures";
name="wiki.documentfoundation.org: How to use digital Signatures">English Wiki
page on digital signatures</link></paragraph>
<paragraph xml-lang="en-US" id="par_id486465" role="paragraph"><link
href="text/shared/guide/digitalsign_send.xhp">Applying digital
signatures</link></paragraph>
<paragraph xml-lang="en-US" id="par_id3448591" role="paragraph"><link
href="text/shared/guide/digitalsign_receive.xhp">Opening a document using
WebDAV over HTTPS</link></paragraph>
diff --git a/source/text/shared/guide/openpgp.xhp
b/source/text/shared/guide/openpgp.xhp
index 35dc2ad60..515569b61 100644
--- a/source/text/shared/guide/openpgp.xhp
+++ b/source/text/shared/guide/openpgp.xhp
@@ -24,7 +24,7 @@
<bookmark_value>file encryption;symmetric keys</bookmark_value>
</bookmark>
<section id="openpgphead">
- <h1 id="hd_id131543693200115"><link
href="text/shared/guide/openpgp.xhp" name="openpgp">Encrypting Documents with
OpenPGP</link></h1>
+ <h1 id="hd_id131543693200115"><variable id="openpgph1"><link
href="text/shared/guide/openpgp.xhp" name="openpgp">Encrypting Documents with
OpenPGP</link></variable></h1>
<paragraph id="par_id531543693200117" role="paragraph"
xml-lang="en-US"><ahelp hid=".">%PRODUCTNAME can encrypt documents using
OpenPGP public key cryptography. The document is encrypted using a symmetric
encryption algorithm.</ahelp></paragraph>
</section>
<section id="howtoget">
_______________________________________________
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
