Joyent SSH key
Andrew Wilkins
andrew.wilkins at canonical.com
Thu Mar 5 01:15:50 UTC 2015
On Thu, Mar 5, 2015 at 1:04 AM, Nate Finch <nate.finch at canonical.com> wrote:
> There is a bug about us defaulting to uploading the user's private id_rsa
> ssh key to joyent as a part of bootstrapping a new server. This is
> obviously a bad thing. bug:
> https://bugs.launchpad.net/juju-core/+bug/1415671
>
> However, the proposed solution (generate our own key and use that) doesn't
> work in practice, because we still need to authenticate with joyent to
> upload the key, which means hoping the user's default ssh key works (and
> assuming it's ok for us to just try it).
>
> My suggested solution is that we do what we do for all the rest of the
> providers, which is to make the user give us authentication credentials in
> the environments.yaml file, and we just use that, and not create anything
> ourselves.
>
> Thoughts welcome.
>
SGTM
There's code (verifyCredentials) in the joyent provider already that tells
the
user what to do if the SSH key or Manta username are invalid. It'd be ideal
if that error message were output whether or not the key is supplied.
> -Nate
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20150305/7d0d3bb5/attachment.html>
More information about the Juju-dev
mailing list