![]() ![]() However, the mimetype and the content of the META-INF folder were not signed. In 3.0 and StarOffice 9.0 the document signature was applied to most content, including macros. ![]() In versions of 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. This status will appear when the signature and certificate are valid, but they were created with a version of before 3.2 or StarOffice before 9.2. 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. Signing other document formats is not supported at the moment. Signing only parts of the document is simply an invalid signature. When you sign a PDF document, then this marking is not used. Metadata of OOXML files are never signed, to be compatible with Microsoft Office. When you sign an OOXML document, then the signature will be always marked with "only parts of the document are signed". ![]() 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. When you sign a document with 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". Now all contents of the files, except the signature file itself (META-INF/documentsignatures.xml) are signed. The signing of contents got changed with 3.2 and StarOffice 9.2. (For documents that were signed with old versions of the software, see note below.) The signature and the certificate are OK, but not all parts of the document are signed. The signature is OK, but the certificates could not be validated. You can see any of the following icons and messages when you open a signed document. 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. If there is a problem with one signature, then the validation result of that one signature is assumed for all signatures. Several documents and macro signatures can exist inside an ODF document. The result of the signature validation is displayed in the status bar and within the Digital Signature dialog. After the change, there will be no sign that you see the original document. Whenever someone changes something in the document, this change breaks the digital signature. You can compare the public key with the public key that is published on the web site of the certificate authority. In addition, the program can show you the public key information from the certificate. If both are the same, the program will signal that you see the original, unchanged document. When someone later opens the document on any computer with a recent version of LibreOffice, the program will compute the checksum again and compare it with the stored checksum. The checksum and your public key are stored together with 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. 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. To sign a document digitally, you need a personal key, the certificate. In LibreOffice, you can digitally sign your documents and macros.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |