Question

Implemented in Kiln 3!

Why does Kiln not support the use of SSH keys for repository authentication? I'm not entirely comfortable with putting passwords in repository URLs; in part, because it inhibits changing them, in part because it means that users' fogbugz passwords are potentially compromised).

Edit: This may be the same as asking: why is http(s) the only protocol supported for repository access?

Also, does this mean that that CI server that pulls code from the repository for test & release has to have a fogbugz/kiln account and password?

Answer 1

The Public repo option allows you to share a Public Repository (read-only), so that may be an option for your CI server. For us, our CI server also tags the release after a build so we've assigned it a FogBugz/Kiln user id.

As far as SSH key support, Kiln uses http/https, not SSH.

Answer 2

Kiln is serving up mercurial over a web server, rather than over SSH, as git does. Mercurial can be configured to allow access via SSH, but Kiln isn't doing it that way (as much as we would like them to). And that should be more clear, Kiln is simply not offering the mercurial <-> SSH option! It's not a mercurial problem!

splattered_bits sums it up well here: http://stackoverflow.com/questions/10961444/accessing-mercurial-repositories-over-ssh