[jdev] Re: TLS and self-signed certs

Matthias Wimmer m at tthias.net
Thu Nov 18 06:38:46 CST 2004


Hi JD!

JD Conley schrieb am 2004-11-12 09:18:46:
> > Not sure ... there are valid reasons to change your s2s certificate:
> > 
> > - Key expired
> > - Key has been compromised
> > - Key has been lost
> > 
> 
> Well, if the cert changed you could then "verify" the key again with a
> dialback and reset the cache if you got the same response from the
> dialback authority.

Allowing dialback to verify new certificates ... I don't think that this
will improve security. It can't be harder than dialback, as an attacker
can always force you to use dialback again (presenting a new
certificate) ... The only thing that changes is, that you get a second
change to take over a host: You get the known certificate of a server.

So I guess using this approach would be even weaker than pure dialback.


Having a trusted body like the JSF, that acts as a registry/CA might be
a solution and I am looking forward to see Peter's proposal ... the
remaining problem might be to verify if someone is allowed to apply for
a certificate.


Tot kijk
    Matthias




More information about the JDev mailing list