![]() ![]() Ensure the path is correct and that you have write permission. ![]() Printf " $3 " | dd of= " $target " bs=1 seek= $(( $1 )) count= " $2 " conv=notrunc status=noneĮcho " $target does not exist or is not writable. Transferred: sent 3268, received 3264 bytes, in -4.Target= " $ " Welcome to GitLab, client_input_channel_req: channel 0 rtype exit-status reply 0ĭebug1: client_input_channel_req: channel 0 rtype reply 0ĭebug1: channel 0: free: client-session, nchannels 1 When using GitBash, everything purrs, but when I try from a plain Windows “cmd” I get a copy of the above screenshots error message.Ĭ:\Users\dummyuser>ssh -Tv LibreSSL 2.6.4ĭebug1: Connecting to SOME IP ADDRESS port 22.ĭebug1: identity file C:\Users\dummyuser/.ssh/id_rsa type 0ĭebug1: key_load_public: No such file or directoryĭebug1: identity file C:\Users\dummyuser/.ssh/id_rsa-cert type -1ĭebug1: identity file C:\Users\dummyuser/.ssh/id_dsa type -1ĭebug1: identity file C:\Users\dummyuser/.ssh/id_dsa-cert type -1ĭebug1: identity file C:\Users\dummyuser/.ssh/id_ecdsa type -1ĭebug1: identity file C:\Users\dummyuser/.ssh/id_ecdsa-cert type -1ĭebug1: identity file C:\Users\dummyuser/.ssh/id_ed25519 type -1ĭebug1: identity file C:\Users\dummyuser/.ssh/id_ed25519-cert type -1ĭebug1: Local version string SSH-2.0-OpenSSH_for_Windows_7.6ĭebug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1ĭebug1: match: OpenSSH_6.6.1 pat OpenSSH_6.6.1* compat 0x04000000ĭebug1: Authenticating to :22 as ‘git’ĭebug1: kex: algorithm: kex: host key algorithm: ecdsa-sha2-nistp256ĭebug1: kex: server->client cipher: MAC: compression: noneĭebug1: kex: client->server cipher: MAC: compression: noneĭebug1: expecting SSH2_MSG_KEX_ECDH_REPLYĭebug1: Server host key: ecdsa-sha2-nistp256 SHA256:l9HnoLc5oBidlZgQf元元8Mv2X4ubBiwX7ChsDCD2D0ĭebug1: Host ‘ ’ is known and matches the ECDSA host key.ĭebug1: Found key in C:\Users\dummyuser/.ssh/known_hosts:1ĭebug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directoryĭebug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,passwordĭebug1: Next authentication method: publickeyĭebug1: Offering public key: RSA SHA256:BIG HASH HERE C:\Users\dummyuser/.ssh/id_rsaĭebug1: Server accepts key: pkalg ssh-rsa blen 535ĭebug1: Authentication succeeded (publickey).Īuthenticated to SOME IP ADDRESSĭebug1: Requesting Entering interactive session.ĭebug1: Remote: Port forwarding disabled.ĭebug1: Remote: Agent forwarding disabled. both, command line (bash) and Windows tools (Sublime Merge) work fine for the same repository.Īdding something odd when I tried the “debug” option in command line. Now I can use both, the subsystem’s ssh key and the Windows ssh key, i.e. So I guess I have to find a way to share this ssh key with Windows somehow… Possibly this is the issue for many folks here.Įdit: Obviously I was right for at least my issue - I followed and created a separate ssh key pair for my Windows 10 system and then added this Windows key to my bitbucket ssh keys. Please make sure you have the correct access rights ![]() ![]() Pulling or pushing using Sublime Merge (Windows) fails with this error message: Permission denied (publickey).įatal: Could not read from remote repository. This setup works fine with a git repo hosted on github, but with my repo hosted on bitbucket, I can only use the git command line tool inside the subsystem (bash shell) for pulling and pushing the repository. I cloned it into the mounted directory, so I can work on the files with the Windows software “Sublime Merge” and “Sublime Text”. I now have the same issue, but the setting might be the problem: I have a git repo from bitbucket cloned using the Ubuntu subsystem in Windows 10. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |