Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-3763

show github trigger ssh key signature

    XMLWordPrintable

Details

    • Feature
    • Resolution: Unresolved
    • Undefined
    • None
    • None
    • quay.io
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%
    • 0

    Description

      Presently when a new trigger is created, the ssh public key is shown to the user. I assume the idea behind that is to allow user to identify key in github once trigger is to be deleted and avoid confusion when other deploy keys in github are available.

      But in github the keys are listed only with their SHA256 fingerprints.

      So user has to save ssh key to a file locally. Then check it's signature:

      ssh-keygen -l -f /tmp/key.pub
      

      Only then is user able to identify which one is the matching key on github.

      It will be user friendly to show the key signature along with the actual key to the user so comparison can much more easily be done.

      btw is there any reason for quay not to remove the deploy key when trigger is removed? This would be even better.

      Attachments

        Activity

          People

            Unassigned Unassigned
            akostadi1@redhat.com Aleksandar Kostadinov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: