Skip to Content.
Sympa Menu

cacert-devel - Re: [website form email]: signing emails in iOS 10

Subject: CAcert Code Development list.

List archive

Re: [website form email]: signing emails in iOS 10


Chronological Thread 
  • From: dirk astrath <dastrath AT gmx.de>
  • To: "Kenneth R. van Wyk" <ken AT krvw.com>, cacert-support AT lists.cacert.org, cacert-devel AT lists.cacert.org
  • Subject: Re: [website form email]: signing emails in iOS 10
  • Date: Thu, 9 Feb 2017 21:28:29 +0000

Hello Kenneth,

> On Feb 9, 2017, at 11:34 AM, Eva Stöwe
> <eva.stoewe AT cacert.org>
> wrote:
>> Because that root was not accepted officially by CAcert, yet.
> Lame excuse, IMHO.

As Eva just wrote:

There was no handover to other members of the software-assessment team,
so everything had to be worked out, checked, investigated etc. later on.

But ...

CAcert is a community project.

Everybody(!) should be able to follow the links (and therefore
procedures) published in our CAcert blog dated 2016-03-13.

But ... as far as I remember there was no feedback about the
resigning-procedure itself, "only" the new root-certificates were used.

Within the last days I spent some hours to reproduce the procedure (and
followed these steps on my own machines using my own root-certificate
(self-signed).

And ... I ran some tests (using different environments/browsers) using
the resigned roots instead of the original ones.

(Hopefully I get at least one other result of somebody following the
described procedure ... ;-) )

What to do next (independing of the above result):

Write some code to ADD (not replace !!!) these roots to our main web site.

How can this be done?

Download our source-code, unpack this code and go to
/cacert/pages/index/3.php. Edit this file and add it to bug 1305 (within
bugs.cacert.org) or send it to me.

I will then review the changes and put it on our test-server (as soon as
I feel comfortable with these changes) for testing.

After everything is tested (and every tester feels comfortable with
these changes) and successfully reviewed it can be deployed on our
productive server.

But ...

I am unable to do this. You do (maybe not you personally, but you as the
community).

Why?

Very easy:

If I do the coding, somebody else from our software-team has to review it.

If you do the coding, I can review it.

So ... please give us a helping hand to solve this issue ... ;-)

Thank you.

Kind regards,

Dirk Astrath
CAcert Software-Assessor


Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.18.

Top of Page