Hi.
I'm trying to test using SSH key to clone a test repository from the cmdline..
I'm screwing up something in following the different sires/examples to try to setup the SSH key to connect to "Github" for a user/repository.
It appears that the "ssh -vT git@github.com" cmd seems to always request a "passphrase" even though the ssh key was created without a passphrase.
I've tried the following cmds on a number of different systems/OS, with the same results.
the cmds are:
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
cat ~/.ssh/github/id_ed25519.pub -- add the key to the github/ssh new key page
(if you notice, no PASSPHRASE)
the ssh private key file is added to the "config" file
ssh -vT git@github.com is run...
. . . debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/crawl_user/.ssh/id_ed25519_g': debug1: No more authentication methods to try. Permission denied (publickey).
which seems to ask for a passphrase!! and then it dies..
I've tried various OS flavors...
looked over different sites..
Anyone with SSH/Fed/Github experience able to provide any thoughts/comments??
I'm sure I'm missing someting subtle, but I can't see it for now.
thanks
Hi
On Sun, 14 Jan 2024 02:27:55 -0500 bruce wrote:
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
<snip>
debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g
The pathnames differ here. Adjust the .ssh/config file to point to:
~/.ssh/github/id_ed25519
hi sorry for the typo..
the file paths matched in my actual test...
the passphrase issue is throwing me
On Sun, Jan 14, 2024 at 2:49 AM Francis.Montagnac@inria.fr wrote:
Hi
On Sun, 14 Jan 2024 02:27:55 -0500 bruce wrote:
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
<snip> > debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g
The pathnames differ here. Adjust the .ssh/config file to point to:
~/.ssh/github/id_ed25519
-- francis -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Sun, Jan 14, 2024 at 3:07 AM bruce badouglas@gmail.com wrote:
hi sorry for the typo..
the file paths matched in my actual test...
the passphrase issue is throwing me
Post your $HOME/.gitconfig file, and your <project>/.git/config file.
For me, I handle SSH check-ins via $HOME/.gitconfig :
$ cat $HOME/.gitconfig [user] email = noloader@gmail.com name = Jeffrey Walton signingkey = 3F537D88ADBC1677 [url "ssh://git@github.com"] pushInsteadOf = https://github.com [url "ssh://git@salsa.debian.org"] pushInsteadOf = https://salsa.debian.org
[push] default = current [gpg] program = gpg2
And then a particular project will use SSH, even though a checkout happened with HTTPS:
$ cd cryptopp-fork $ cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/noloader/cryptopp fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master [remote "upstream"] url = https://github.com/weidai11/cryptopp fetch = +refs/heads/*:refs/remotes/upstream/*
Jeff
Hi Jeffery,
Thanks for the reply. In my test, I don't configure a $HOME/.gitconfig file, and your <project>/.git/config file.
The weird thing, i'm seeing a number of other people who have had similar issues with accessing git@github.com....
and they seem to discuss using the ssh-agent for the key.
But none of the tutorials I've seen indicate you need to use a keyring..
thanks
On Sun, Jan 14, 2024 at 3:54 AM Jeffrey Walton noloader@gmail.com wrote:
On Sun, Jan 14, 2024 at 3:07 AM bruce badouglas@gmail.com wrote:
hi sorry for the typo..
the file paths matched in my actual test...
the passphrase issue is throwing me
Post your $HOME/.gitconfig file, and your <project>/.git/config file.
For me, I handle SSH check-ins via $HOME/.gitconfig :
$ cat $HOME/.gitconfig [user] email = noloader@gmail.com name = Jeffrey Walton signingkey = 3F537D88ADBC1677 [url "ssh://git@github.com"] pushInsteadOf = https://github.com [url "ssh://git@salsa.debian.org"] pushInsteadOf = https://salsa.debian.org
[push] default = current [gpg] program = gpg2
And then a particular project will use SSH, even though a checkout happened with HTTPS:
$ cd cryptopp-fork $ cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/noloader/cryptopp fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master [remote "upstream"] url = https://github.com/weidai11/cryptopp fetch = +refs/heads/*:refs/remotes/upstream/*
Jeff
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 1/14/24 10:48, bruce wrote:
Thanks for the reply. In my test, I don't configure a $HOME/.gitconfig file, and your <project>/.git/config file.
The weird thing, i'm seeing a number of other people who have had similar issues with accessing git@github.com....
and they seem to discuss using the ssh-agent for the key.
But none of the tutorials I've seen indicate you need to use a keyring..
I've been using github for years over ssh with no issues. I don't add anything to the .gitconfig file or the project. I have created a separate key for use with github, registered it in my account, and added an entry in the .ssh/config to tell ssh to use that key. From there, it just works.
On 1/13/24 23:27, bruce wrote:
I'm trying to test using SSH key to clone a test repository from the cmdline..
I'm screwing up something in following the different sires/examples to try to setup the SSH key to connect to "Github" for a user/repository.
It appears that the "ssh -vT git@github.com" cmd seems to always request a "passphrase" even though the ssh key was created without a passphrase.
I don't understand why you're trying to ssh to github. That's not going to work. You need to use the git command to do the clone.
bruce writes:
It appears that the "ssh -vT git@github.com" cmd seems to always request a "passphrase" even though the ssh key was created without a passphrase.
That's because you don't ssh to github.
Once the key is set up, and added to your github profile, "git clone" clones the repository. This does use the ssh protocol, but there is no direct ssh access to github.
Hi Samuel.
Yeah, trying to clone using cmdline/ssh
I can clone using https.
The steps I've tried don't seem to connect.
login as foo eval `ssh-agent -s` ssh-add ~/.ssh/id_ed25519_g Enter passphrase for /home/crawl_user/.ssh/id_ed25519_g:
the perms for chmod 700 /home/foo/.ssh chmod 600 .ssh/* id_ed25519_g id_ed25519_g.pub
login to another term:: run ssh-add -L ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwIufIK2RJZe4UStofMA8eoD45PALWKTz8gmHUFVMs+fkjnOVB/huo973wPGGg8PkEQu1tjl7hh3MmjNU+LykZykbRSm6jTBU7K4EUtGhF7AMWsPjyrLwrlmtL36O74ucFVNEb0uih8y827uP3cKEGX/gi7m8FHFzn0sR547jB8s3q2mBey/n+iKKB3WU0BgGSnYUdWQTKK51J4mNEtkdr/zV/0xQ+ICMjLRuIT4cFhKJ1SRBN4GeyqXzH8tOx4a7aeNMgu2KyoZUwPTXg+nQQh6TNt8v1VfOvz4S4T+uR4XakQeIAMSrDn1TSZ7+P6bNLk3jNjF8RJPnr59QQEPQhw== root@foo ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAnB5GhprThFO3uQunWqnMVef7lwH2PT6uOw0vMsrS/yD8Okxl7STcnYY+c80CAlz4pORiVSvsmCtpod5z/ke73hZzqXevwskrixZGsI2pW8F8bsquttZAiKdutppIo2ILcG1ZL4zVrizWh4Ad6ywNt/N0ZZdbwjEkNDb6RCgFyDfZc/fCZRy2yw5qqG5C7t0EGvybNVRBfrXeSAQcyRW9CESdBDVFWe7DRI5SrNoLSrJfEUOhoTz+uP5tZLLpKq+6vYwQfuLS9DoUjULrtnPakmE0FmqyVA10YdAONWlAoVyWsT9Jxq21QglXf6h7xATp4HtxpwgU7kxoqBtjJClDpQ== root@foo are the items that are returned... which is weird.. not sure how these got there...
I'm trying to remove/delete these items, so when I do a "ssh-add -L" it returns ""
I've tried to "delete" the items by using portions of the content with no luck..
ie.. ssh-add -L | grep -F '7kxoqBtjJClDpQ=' | ssh-add -d - returns... Identity removed: (stdin) RSA (root@foo)
but the "ssh-add -L" still returns the same items. This is still the same action even when logging out/back in the term....
the steps should be login as user foo setup the sshkey
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/id_ed25519 -q -N ''
making sure the perms are set to the correct perms cat ~/.ssh/id_ed25519 cat ~/.ssh/id_ed25519.pub -- add the key to the github/ssh new key page
using the pub key, add it to the "github" webpage in the new sshkey dialog
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
which seems to ask for a passphrase!! and then it dies..
I've tried to run the basic process....
setup the /.ssh/config Host github.com HostName github.com ## 67.205.151.11 User git AddKeysToAgent yes /home/crawl_user/.ssh/id_ed25519_g
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
creates the new key pub/priv cat ~/.ssh/github/id_ed25519.pub cat ~/.ssh/github/id_ed25519 -- add the key to the github/ssh new key page
. . . debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/crawl_user/.ssh/id_ed25519_g': debug1: No more authentication methods to try. Permission denied (publickey).
which seems to ask for a passphrase!! and then it dies..
so...... try using the sshgen eval $(ssh-agent -s)
ssh-add ~/.ssh/id_ed25519_g Enter passphrase for /home/crawl_user/.ssh/id_ed25519_g:
log into a sep term run ssh-add -L
==>> there should be the key from the id_ed25519_g
which should then allow you to run ssh -vT git@github.com to test.... on success....
you could then clone the repos
git clone git@github.com:foo/test.git
thoughts...
thanks..
On Sun, Jan 14, 2024 at 3:12 PM Samuel Sieb samuel@sieb.net wrote:
Have you actually tried cloning? Is there a problem you're trying to solve? -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Mon, Jan 15, 2024 at 12:52 AM bruce badouglas@gmail.com wrote:
[...]
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
You have been told twice that this is wrong. Both Samuel Sieb and Sam Varshavchik told you so.
If you think your setup is ready, then perform a clone and then a test commit on a test branch.
It has been my experience that keys are Ok and the agent is Ok (assuming you shared the public key on the Git server). The problems come with getting your gitconfig's right. And the easiest way is to show someone a working gitconfig rather than trying to regurgitate git commands.
Jeff
On 1/14/24 22:04, Jeffrey Walton wrote:
On Mon, Jan 15, 2024 at 12:52 AM bruce badouglas@gmail.com wrote:
[...]
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
You have been told twice that this is wrong. Both Samuel Sieb and Sam Varshavchik told you so.
Actually, this is correct. :-) I suggest running it first without the "-v" because it dumps a lot of stuff. If the first run doesn't work, then add it to see what's going wrong.
$ ssh -T git@github.com Hi ssieb! You've successfully authenticated, but GitHub does not provide shell access.
On Mon, Jan 15, 2024 at 1:25 AM Samuel Sieb samuel@sieb.net wrote:
On 1/14/24 22:04, Jeffrey Walton wrote:
On Mon, Jan 15, 2024 at 12:52 AM bruce badouglas@gmail.com wrote:
[...]
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
You have been told twice that this is wrong. Both Samuel Sieb and Sam Varshavchik told you so.
Actually, this is correct. :-) I suggest running it first without the "-v" because it dumps a lot of stuff. If the first run doesn't work, then add it to see what's going wrong.
$ ssh -T git@github.com Hi ssieb! You've successfully authenticated, but GitHub does not provide shell access.
My apologies to Bruce.
Jeff
On Mon, Jan 15, 2024 at 1:06 AM Jeffrey Walton noloader@gmail.com wrote:
On Mon, Jan 15, 2024 at 12:52 AM bruce badouglas@gmail.com wrote:
[...]
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
You have been told twice that this is wrong. Both Samuel Sieb and Sam Varshavchik told you so.
If you think your setup is ready, then perform a clone and then a test commit on a test branch.
Hi Jeffery.
I did do a test as user foo git clone git@github.com:foo/test.git
it returns , , , Enter passphrase for key '/home/crawl_user/.ssh/id_ed25519_g': debug1: No more authentication methods to try. git@github.com: Permission denied (publickey).
which as I've stated appears to be asking for a passphrase even though none was used to create the "key"
As to the issue you guys have with running ---- ssh -vT git@github.com, I'm not sure why, as this appears to simply test the connection via ssh. but again, running this gets the same
Enter passphrase for key '/home/crawl_user/.ssh/id_ed25519_g': debug1: No more authentication methods to try. git@github.com: Permission denied (publickey).
but again, running this gets the same issue -----------------------------------------------------------
It has been my experience that keys are Ok and the agent is Ok (assuming you shared the public key on the Git server). The problems come with getting your gitconfig's right. And the easiest way is to show someone a working gitconfig rather than trying to regurgitate git commands.
Jeff
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 1/14/24 21:50, bruce wrote:
[snip lots of stuff] You're doing way too many unnecessary things. I noticed that I was using an rsa key, so I decided to follow the steps to add a new ed25519 key.
login as user foo setup the sshkey
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/id_ed25519 -q -N ''
You might not want to use "-q" as it might be hiding something you need to know. I create a specific key for github instead of using the default file. That also makes it easier to copy around to other systems.
What I used and hit enter for the password: ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519.git
-- add the key to the github/ssh new key page
using the pub key, add it to the "github" webpage in the new sshkey dialog
Did this.
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
I was not aware of this handy test before.
which seems to ask for a passphrase!! and then it dies..
I've tried to run the basic process....
setup the /.ssh/config Host github.com HostName github.com ## 67.205.151.11 User git AddKeysToAgent yes /home/crawl_user/.ssh/id_ed25519_g
Where did that "_g" on the end come from? It doesn't match any of your commands.
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
creates the new key pub/priv cat ~/.ssh/github/id_ed25519.pub cat ~/.ssh/github/id_ed25519 -- add the key to the github/ssh new key page
. . . debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/crawl_user/.ssh/id_ed25519_g': debug1: No more authentication methods to try. Permission denied (publickey).
which seems to ask for a passphrase!! and then it dies..
Compare the key you generated with the key it's trying. Apparently you either created another key with a password or it just doesn't exist and thinks it needs a password. Fix your config file.
Hi Sam.
Ok, so you did a similar test using steps that I've provided, and it runs correctly.
This is cool! -- So this points to "user" err, or something weird...
If I may, are you running everything as user 'foo' or 'root'? Are you running everything in the same term window/process?
And, can I ask if you can post the relevant section of your config file that pertains to the github issue?
I'll rerun the "test" I've been doing, and post the steps/results. I'm doing this both with fed as well as ubuntu to see if there's any weirdness.
Thanks for your posts on this!
On Mon, Jan 15, 2024 at 1:23 AM Samuel Sieb samuel@sieb.net wrote:
On 1/14/24 21:50, bruce wrote:
[snip lots of stuff] You're doing way too many unnecessary things. I noticed that I was using an rsa key, so I decided to follow the steps to add a new ed25519 key.
login as user foo setup the sshkey
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/id_ed25519 -q -N ''
You might not want to use "-q" as it might be hiding something you need to know. I create a specific key for github instead of using the default file. That also makes it easier to copy around to other systems.
What I used and hit enter for the password: ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519.git
-- add the key to the github/ssh new key page
using the pub key, add it to the "github" webpage in the new sshkey dialog
Did this.
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
I was not aware of this handy test before.
which seems to ask for a passphrase!! and then it dies..
I've tried to run the basic process....
setup the /.ssh/config Host github.com HostName github.com ## 67.205.151.11 User git AddKeysToAgent yes /home/crawl_user/.ssh/id_ed25519_g
Where did that "_g" on the end come from? It doesn't match any of your commands.
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
creates the new key pub/priv cat ~/.ssh/github/id_ed25519.pub cat ~/.ssh/github/id_ed25519 -- add the key to the github/ssh new key page
. . . debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/crawl_user/.ssh/id_ed25519_g': debug1: No more authentication methods to try. Permission denied (publickey).
which seems to ask for a passphrase!! and then it dies..
Compare the key you generated with the key it's trying. Apparently you either created another key with a password or it just doesn't exist and thinks it needs a password. Fix your config file. -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Hi Sam!!!
ok...
user err!!
Thanks for replying/posting your "ssh-keygen" cmd..
login as user create sshkey priv/pub id_ed25519_g //ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/id_ed25519_g -q -N '' --is "C" for passphrase? --per Sam/fed email thread, test without "-C..." ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519_g
The diff being the removal of the "-q -N" attributes -N -- new passphrase -q --- don't know what this does???
running the cmd, then generates the priv/pub sshkey...
-clear out the 'sshkey' in the github webpage/settings https://github.com/settings/keys
on/in the cmdline/term cat ~/.ssh/id_ed25519_g.pub do a copy of the output, and add the results to/as the key in the github sshkey dialog
this sets the "new" sshkey on the remote/github app/site
from the cmdline/client..
do a test: ssh -vT git@github.com
this succeeds.. as expected... sshkey/connection is valid/works
test the clone for the local side,, git clone git@github.com:foo/clist.git
local clone/dir is created... success!!!
next.. to test basic local git actions file changes, repo changes "upload" repo changes to the remote github site/app etc...
(ps -- so all it took was to have the correct ssh-keygen cmd!!) -- was pretty sure it was something subtle/simple.
anything I should test??
thanks!
On Mon, Jan 15, 2024 at 7:50 AM bruce badouglas@gmail.com wrote:
Hi Sam.
Ok, so you did a similar test using steps that I've provided, and it runs correctly.
This is cool! -- So this points to "user" err, or something weird...
If I may, are you running everything as user 'foo' or 'root'? Are you running everything in the same term window/process?
And, can I ask if you can post the relevant section of your config file that pertains to the github issue?
I'll rerun the "test" I've been doing, and post the steps/results. I'm doing this both with fed as well as ubuntu to see if there's any weirdness.
Thanks for your posts on this!
On Mon, Jan 15, 2024 at 1:23 AM Samuel Sieb samuel@sieb.net wrote:
On 1/14/24 21:50, bruce wrote:
[snip lots of stuff] You're doing way too many unnecessary things. I noticed that I was using an rsa key, so I decided to follow the steps to add a new ed25519 key.
login as user foo setup the sshkey
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/id_ed25519 -q -N ''
You might not want to use "-q" as it might be hiding something you need to know. I create a specific key for github instead of using the default file. That also makes it easier to copy around to other systems.
What I used and hit enter for the password: ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519.git
-- add the key to the github/ssh new key page
using the pub key, add it to the "github" webpage in the new sshkey dialog
Did this.
before cloning a repos, test to make sure things work...
ssh -vT git@github.com this should return success if everything works correctly
I was not aware of this handy test before.
which seems to ask for a passphrase!! and then it dies..
I've tried to run the basic process....
setup the /.ssh/config Host github.com HostName github.com ## 67.205.151.11 User git AddKeysToAgent yes /home/crawl_user/.ssh/id_ed25519_g
Where did that "_g" on the end come from? It doesn't match any of your commands.
ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/github/id_ed25519 -q -N ''
creates the new key pub/priv cat ~/.ssh/github/id_ed25519.pub cat ~/.ssh/github/id_ed25519 -- add the key to the github/ssh new key page
. . . debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/crawl_user/.ssh/id_ed25519_g debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/crawl_user/.ssh/id_ed25519_g': debug1: No more authentication methods to try. Permission denied (publickey).
which seems to ask for a passphrase!! and then it dies..
Compare the key you generated with the key it's trying. Apparently you either created another key with a password or it just doesn't exist and thinks it needs a password. Fix your config file. -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 1/15/24 05:25, bruce wrote:
(ps -- so all it took was to have the correct ssh-keygen cmd!!) -- was pretty sure it was something subtle/simple.
Read my previous message more carefully. It's sort of related to the keygen command but only because the file you created with the keygen didn't match the file you specified in the ssh config file.
On 1/15/24 05:25, bruce wrote:
Thanks for replying/posting your "ssh-keygen" cmd..
login as user create sshkey priv/pub id_ed25519_g //ssh-keygen -t ed25519 -C 'your@email.com' -f ~/.ssh/id_ed25519_g -q -N '' --is "C" for passphrase?
"-C" specifies the "comment" at the end, which is usually an email address. The keygen will default to putting username@hostname.
--per Sam/fed email thread, test without "-C..." ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519_gThe diff being the removal of the "-q -N" attributes -N -- new passphrase -q --- don't know what this does???
"-N" specifies the passphrase to use, so it won't ask you. "-q" is "quiet", so it will only print errors.
-
bruce -
Francis.Montagnac＠inria.fr -
Jeffrey Walton -
Sam Varshavchik -
Samuel Sieb