Date: prev next · Thread: first prev next last

Re: [libreoffice-conference] Keysigning key submission period closed, keylist published


On Tue, Sep 2, 2014 at 4:27 PM, Italo Vignoli <italo.vignoli@gmail.com> wrote:
Pete Stephenson wrote:

Hopefully that straightens things out a bit. If you have any other
questions, let me know.

I will try to follow the procedure on my Linux machine (on the Mac there
is no way to make it work), and I hope to find a printer once I have
generated the file (the first part until the hashes calculation is
already done, and I have a PDF of the text file).

You can always download the file to one computer, print it out, then
copy the file to a different computer to calculate the hashes. Just be
sure that the method of copying (a) doesn't alter the file and (b) is
reasonably secure. Using a USB flash drive to move the file between
computers would be reasonable in most situations I can imagine.

Please be sure to calculate the hashes of the keylist text file, and
not the PDF you've produced, otherwise they won't match the hashes of
the official list.

Cheers!
-Pete

-- 
Pete Stephenson

-- 
To unsubscribe e-mail to: conference+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/conference/
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.