Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Re: [board-discuss] CAcert Organization Validation


Hi,

Florian Effenberger wrote on 2012-02-07 10:48:
Although CAcert isn't included in many major browsers and mail clients,
I think this sounds like a good thing to do, and I'll follow-up as soon
as I have details.

...and I forgot the most important thing to mention: Why we should do so. ;-)

Although it is not enforced, it might make sense to have meeting minutes and official BoD decisions signed in the future, to ensure they are valid, and everyone can verify. For that, it would be desirable for every BoD and MC member + deputy to have their own certificate.

The reason for using S/MIME (X.509) rather than GPG is that

1. LibreOffice can sign ODT with X.509 certificates
2. PDFs can be signed using them as well
3. most mail clients support them out of the box

Florian

--
Florian Effenberger <floeff@documentfoundation.org>
Chairman of the Board at The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff

--
Unsubscribe instructions: E-mail to board-discuss+help@documentfoundation.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.documentfoundation.org/www/board-discuss/
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.