Re: github cloning from cmdline

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx' -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@xxxxxxxxxx
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@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..

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@xxxxxxxxxx
to test....
 on success....

you could then clone the repos

git clone git@xxxxxxxxxx:foo/test.git

thoughts...

thanks..





On Sun, Jan 14, 2024 at 3:12 PM Samuel Sieb <samuel@xxxxxxxx> wrote:
>
> Have you actually tried cloning?
> Is there a problem you're trying to solve?
> --
> _______________________________________________
> 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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux