I have a single ssh key that I use for authentication, connected to my email address. Github gets the public key (as does the git config on any other remote git server I interact with). After any reboot, the first command I run is ssh-add so that all terminals I open already have my credentials (nobody else has access to this computer), and interaction with github and others is seamless.
Ok, I thought I was getting the upper hand with this:
$ xclip -sel clip < id_rsa.pub
But then...
fritz@laptop:~/.ssh$ ssh -T tallharry66@gitlab.com
The authenticity of host 'gitlab.com (2606:47...:a9b9)' can't be estab
+lished.
ECDSA key fingerprint is SHA256:....w.
Are you sure you want to continue connecting (yes/no/[fingerprint])? y
+es
Warning: Permanently added 'gitlab.com,2606:4700:....' (ECDSA) to the
+list of known hosts.
tallharry66@gitlab.com: Permission denied (publickey).
fritz@laptop:~/.ssh$
So I'm not there yet. Was the .pub one the right one to give to gitlab?
(I hope I haven't left my auth key bare here.)
is @gitlab.com right?
Fishing for tips,
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
