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

[board-discuss] CAcert mail certificates


Hello,

I just got a call from the CAcert folks. Unfortunately, right now, there is no way that you can create your own private key when being validated for an organization. The only option for the moment is that I, as organization administrator, create your certificate including the private key and send it to you.

The certificate then will contain your full name, your mail address @documentfoundation.org, "The Document Foundation" as entity name, plus your official role.

I promise to immediately delete the private key, but theoretically, of course, this would enable me to read mails encrypted to you. CAcert is working on an improvement of their process, but there is no ETA yet.

If you are still interested, please drop me a private message.

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.