CAcert Code Development list.

[Dieter Hennig <dieter.hennig AT id.ethz.ch>]

Dear all,

sorry  for this last mail, it run away too fast

Dieter Hennig schrieb am 17.03.2010 01:30:
> Dear all,
> 
> Ian G schrieb am 17.03.2010 01:17:
>>  So take this opportunity to advance the policy at the same time.
> 
> Okay for me, the patch themselves is important for us and the
> possibility to choose between CSR or centralized private key storage is
> also good for us.
>

Please look at this:

http://www.bj.admin.ch/bj/de/home/themen/wirtschaft/gesetzgebung/abgeschlossene_projekte/elektronische_signatur.html


And if we would use client-certificates for staff member as org-member
of CAcert, at least to my understanding, we had to develop an internal
policy, like for code-signing, which has to be coordinated with all our
staff-members.

This is not again CAcert at all, this is an opportunity for
FOSS-communities to show up, what freedom/limitation means.


Best Regards


Dieter



-- 
Dieter Hennig
Informatikdienste/Helpdesk
ETH Zuerich, STB G 18.2
8092 Zuerich, Stampfenbachstr. 69
Tel: +41 44 632 4278
Fax: +41 44 632 1900

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature