Comment #1 by ppatters:
Hmmm... for the "validate the certificate" part, maybe you should take
a look at
pathfinder :)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Comment #2 by apenwarr:
Don't worry I was thinking of exactly that. Since we're running dbus
and all anyway :)
Although for small installations, hardcoding the certificates we want
to accept is
also an important feature to have.
Comment #3 by ppatters:
Just don't forget that if you hardcode the certificates, you have to
either force an
update (eventually - certificates have a fixed lifetime), or ignore certificate
validity, in which case, why not just use some form of shared secret instead.
Certificates are really only useful if you have a large number of keys
to manage -
for a situation where you have a small number (10 or so), some form of
shared secret
is actually easier and less confusing for most people to handle.