[
https://issues.jboss.org/browse/JBIDE-8096?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8096:
-----------------------------------------
ok so we decided the following:
1) we add a text-field to the "Manage keys" dialog that is initialized with the
path that is set in the SSH-preferences.
2) In the "Manage keys" dialog we store keys to the given (text-field) path and
add it to the private keys of the SSH-preferences
3) we ask the user if he agrees that the new key's stored and added
4) We warn the user if he launches an instance with a key that is not stored locally &
added to the private key
1) is necessary since you can add keys to the (ssh-prefs) private keys full path. SSH-home
in the prefs is just a sensitive default to store keys but you may choose any other
location and add the key to the private keys.
4) is a pragmatic approach since we are close to CR1. We can implement that dialog later
on. There may be usecases where the key that was used to launch the instance is not
identical to the key that is used to connect to the ssh-daemon that runs on it.
Launch instance wizard: key that you select to launch the instance is
not added to the ssh preferences
------------------------------------------------------------------------------------------------------
Key: JBIDE-8096
URL:
https://issues.jboss.org/browse/JBIDE-8096
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira