Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-8253

Launch instance wizard: you get warned of a key that is not known to the ssh-subsystem even if the key is listed in the ssh-prefs

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.2.0.Final, 3.2.1.M1
    • 3.2.0.CR1
    • deltacloud
    • None
    • Hide

      1) choose "Launch instance" in the context menu of the cloud viewer
      2) choose "Manage"
      3) make sure you store the new key to a local folder (checkbox) and that the folder is the folder used as ssh-home directory to the ssh-subsystem (Preferences->General->Network Connections->SSH2->SSH2 Home - ex. /home/adietisheim/.ssh)
      4) create a new key (ex. key)
      5) go to Preferences->General->Network Connections->SSH2
      6) remove your key from the "Private keys" (notice that its listed with full path. ex. /home/adietisheim/.ssh/key.pem)
      7) add it again using the filename only (ex. key.pem)
      8) "Launch instance"
      9) choose the key you just added to the ssh private keys (ex. key.pem)
      10) hit "Finish"

      Result:
      You get warned in a dialog that the key you indicated (ex. key.pem) is not known to the ssh-subsystem. This is not true since you added it to the ssh-privatekeys but used a relative path.

      Expected:
      No warning.

      Show
      1) choose "Launch instance" in the context menu of the cloud viewer 2) choose "Manage" 3) make sure you store the new key to a local folder (checkbox) and that the folder is the folder used as ssh-home directory to the ssh-subsystem (Preferences->General->Network Connections->SSH2->SSH2 Home - ex. /home/adietisheim/.ssh) 4) create a new key (ex. key) 5) go to Preferences->General->Network Connections->SSH2 6) remove your key from the "Private keys" (notice that its listed with full path. ex. /home/adietisheim/.ssh/key.pem) 7) add it again using the filename only (ex. key.pem) 8) "Launch instance" 9) choose the key you just added to the ssh private keys (ex. key.pem) 10) hit "Finish" Result: You get warned in a dialog that the key you indicated (ex. key.pem) is not known to the ssh-subsystem. This is not true since you added it to the ssh-privatekeys but used a relative path. Expected: No warning.

    Attachments

      1. key-is-in-prefs.png
        key-is-in-prefs.png
        47 kB
      2. KeyPathCheck.patch
        3 kB
      3. NonSshKeyDecoration.patch
        4 kB
      4. NonSshKeyDecoration-3.patch
        5 kB
      5. NonSshKeyDecoration-4.patch
        5 kB
      6. NonSshKeyDecoration-5.patch
        5 kB
      7. unknwon-key-warning.png
        unknwon-key-warning.png
        53 kB

      Issue Links

        Activity

          People

            adietish@redhat.com André Dietisheim
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: