Yeah man, you nailed it. I changed the putty-oriented environment variable to point at OpenSSH. previous: declare -x GIT_SSH="C:\Program Files\PuTTY\plink.exe" fixed: declare -x GIT_SSH="C:\Windows\System32\OpenSSH\ssh.exe" $ git push sourceforge main Warning: Permanently added the ED25519 host key for IP address '1x6.1x5.x8.x6' to the list of known hosts. Enumerating objects: 59, done. Counting objects: 100% (59/59), done. Delta compression using up to 8 threads Compressing objects: 100% (50/50),...
Would/could that screw up SSH to GitHub? On Thursday, January 5, 2023 at 05:07:30 PM CST, Dave Brondsema <brondsem@users.sourceforge.net> wrote: Yea I think putty is the problem. If you remove the GIT_SSH environment variable, like export GIT_SSH= and then try, will it work? Sincerely, SourceForge Support [site-support:#24111] netwonk: sourceforge update of github code Status: open Created: Mon Dec 19, 2022 06:21 PM UTC by Jack Gallagher Last Updated: Thu Jan 05, 2023 07:37 PM UTC Owner: nobody My...
Thanks! $ git remote -v origin https://github.com/jackg23x/netwonk.git (fetch) origin https://github.com/jackg23x/netwonk.git (push) sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code (fetch) sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code (push) $ echo $GIT_SSH C:\Program Files\PuTTY\plink.exe wow -it's using putty -- I thought it was using openssh $ ssh -v git.code.sf.net OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting...
Yeah, you keep replying to old notes from me, so I don't know if you see the most recent.I can see why you would be ready to bail on this, but give me a moment: Anyway, I mentioned I can create a shell connection using the command ssh -t jackg23@shell.sourceforge.net create, so the keys are working. I'm using ed25519 rather than rsa. That's telling me the key setup is OK, right? I can upload changes from git local repos to the Github remote repos. The only thing I can't do is push from git to sourceforge.I...
Thanks for the reply -- this has progressed past my initial note you show below. I do have the SSH key set up.I am able to create a shell and connect that way using the key, but no luck on Git. I'm running Git on a Windows box here, and I'm invoking this command from the source directory in Git Bash,but I'm still getting the same failure: MINGW64 ~/Documents/GitHub/netwonk (main) $ git push sourceforge main Keyboard-interactive authentication prompts from server: fatal: protocol error: bad line length...
It seems like I'm almost there.I'm stuck on this: $ git push sourceforge main Keyboard-interactive authentication prompts from server: fatal: protocol error: bad line length character: | Pa I've reviewed all my ssh key stuff, and it seems like it should be fine. But, no luck yet.What am I missing?Thanks,Jack On Thursday, December 22, 2022 at 01:42:56 PM CST, Dave Brondsema <brondsem@users.sourceforge.net> wrote: When you run the git remote add ... command, make sure you're in the directory of your...
Thanks much Dave, I'll have at it. On Thursday, December 22, 2022 at 01:42:56 PM CST, Dave Brondsema <brondsem@users.sourceforge.net> wrote: When you run the git remote add ... command, make sure you're in the directory of your git repository. The error message you got means you weren't in the right directory. And also you are correct you don't a space for this command. git remote add sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code would be the full command to use for this. Sincerely, SourceForge...
I'm hitting a further issue. this is my git clone text: ssh://jackg23@git.code.sf.net/p/netwonk/code netwonk-code Here's what I get: C:\Users\jackg>git remote add sourceforge ssh://jackg23@git.code.sf.net/p/netwonk/code netwonk-code fatal: not a git repository (or any of the parent directories): .git The empty space doesn't seem right in the url. Things I've tried don't affect anything. Ideas? thanksJack On Monday, December 19, 2022 at 03:52:29 PM CST, SourceForge Support sf-support@users.sourceforge.net...