Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have setup a Github ssh key according to instructions. I did the same for Gitlab, also according to instructions. And it works.
But what I would like to know is what pubkey of Github is related to what files on my harddisk.
In other words, can I identify what private keys on my harddisk relates to the Github pub key on Github?
Well, the name is the problem of course. My Github key gives a line like bc:27:ac:34: etc.
That doesn't offer much of identification. Isn't there a command line command that I can use so that I can identify which public key is used in Github? And not based on name?
Well, the name is the problem of course. My Github key gives a line like bc:27:ac:34: etc.
That would be the fingerprint in the form of an MD5 checksum, a outdated format. SHA256 is the current best practice. However, be that as it may, you can use ssh-keygen to check your existing keys and display their fingerprints. Then you can manually find a match and rename the key files to something more mnemonic.
Code:
for f in ~/.ssh/*.pub;
do
echo
echo $f
ssh-keygen -E md5 -lf $f;
done
Last edited by Turbocapitalist; 02-12-2019 at 02:29 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.