Re: TLS key for api.ftp-master.debian.org
On Fri, 07, Nov, 2014 at 04:53:44PM +0000, Ian Jackson spoke thus..
> Thanks for helping with this. When I spoke to ftpmaster et al about
> this before, we had a conversation about TLS public keys and
> I would like the DAK API TLS security to be rooted in a
> Debian-controlled public key distributed in a package in Debian,
> rather than using a public CA.
> What I suggested is here:
> (in `Part II').
> I provided rationale for this approach, rather than using a
> conventional https public CA, here:
> (Noodles pointed out a little laterthat I should have meant
> the debian-archive-keyring package, not the debian-keyring one.
> Mark Hymers agreed with me here:
> I provided some scripts for key and cert generation, here:
I agree with the concept that having a known public key is helpful so
that programs can check they're talking to who they think they are. I
did say last year (although I just had to re-read) that a single use CA
was the better option. I'm not so sure about it now however.
As far as I'm concerned, the main thing if we're going to publicise the
key is to have a clean rollover strategy. Frankly, I'm not sure that I
want to commit to dealing with this side of it - SSL certs are part of
the infrastructure really, and I'm inclined to defer to DSA on this.
It's also not likely that this is the only "web" service in Debian where
we could do with a method of knowing whether we're talking to the right
service or not. The question is, who wants to take responsibility for
sorting out the certs etc. I'm not going to tell whoever it is (and I
don't want it to be me) how to do that job.
Mark Hymers <mhy at debian dot org>
"I told you I was ill"
The epitaph of Spike Milligan (1918-2002)