Brian "bex" Exelbierd is the RHEL Community Business Owner and works to inform the RHEL roadmap with community efforts and to support Operating System communities. At Red Hat, Brian has worked as a technical writer, software engineer, content strategist, community architect and now as a product manager. Brian spends his day enabling Red Hat Operating System communities and easing the way for RHEL to participate in the great things they do. Before Red Hat, Brian worked with the University of Delaware as the Director of Graduate and Executive Programs in the Alfred Lerner College of Business and Economics and as a Budget Analyst. Brian's background in software engineering stretches back years before his university work and includes stints in both business and government. Many of his projects are the "glue code" or interstitial pieces that fill the spaces between systems, providing continuity and ease of use.
He writes on his blog at winglemeyer.org.
Authored Comments
Hi @boxofrox
If you import existing SSH keys into your GPG key you are not changing your keys. Therefore any machines that were already set up with your SSH key in their authorized_keys file will continue to work with the new GPG stored key.
The quote you include is meant to mean that you don’t have to updated your already authorized hosts. There is no system to take care of that for you automatically, you always have to do a login or ssh-key-copy to get the initial setup.
In the third part of the series I talk about managing multiple imported SSH keys to avoid key try attempt fails.
Hi Blake, As I recall the monkeysphere project can handle most, but not all formats with pem2openpgp. Did you try that? If not, I encourage you to engage with that upstream.