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@xxxxxxxxx' -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@xxxxxxxxxx
this succeeds.. as expected... sshkey/connection is valid/works
test the clone for the local side,,
git clone git@xxxxxxxxxx: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@xxxxxxxxx> 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@xxxxxxxx> 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@xxxxxxxxx' -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@xxxxxxxxxx
> > > 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@xxxxxxxxx' -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@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > 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@xxxxxxxxxxxxxxxxxxxxxxx
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
