Hi Christian
Christian Lohmaier-2 wrote > You need to import the key into your keyring, so that the tool can > actually verify it. I imported the key and, although the message is not clear, I guess this will have to do... >From the working installer <http://nabble.documentfoundation.org/file/n4074811/GPGcheckok.png> from the corrupted installer <http://nabble.documentfoundation.org/file/n4074811/GPGcheck_corrupted.png> I was expecting a clear "The file is corrupted/invalid"... For future reference, the way to import a key using GPG4Win is to click on the Kleopatra button "Lookup Certificates on Server", type libreoffice in the Find field, click on the Search button and then from the extensive list choose LibreOffice Build Team (CODE SIGNING KEY) and click on Import. Thanks! Pedro -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-ANN-LibreOffice-4-1-2-RC2-test-builds-available-tp4074723p4074811.html Sent from the QA mailing list archive at Nabble.com. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
