![]() I have attached what (I'm pretty sure) is an instance of the failure in the SmartGit application log:ġ782732 ( 12:18:56,653) INFO - Executing following command: "C:\Program Files\Git\bin\git.exe" ls-remote ssh://initio-dev01/INIT/ refs/heads/ġ782732 ( 12:18:56,653) INFO - in directory: nullġ783049 ( 12:18:56,970) INFO rver - received command: sshġ786438 ( 12:19:00,359) INFO - stderr: fatal: 'C:/Program Files (x86)/Git/INIT/' does not appear to be a git repositoryġ786438 ( 12:19:00,359) INFO - fatal: 'C:/Program Files (x86)/Git/INIT/' does not appear to be a git repositoryġ786439 ( 12:19:00,360) ERROR - .TransportManager: Receive thread: error in receiveLoop: socket closedġ786763 ( 12:19:00,684) INFO - stderr: fatal: The remote end hung up unexpectedlyġ786763 ( 12:19:00,684) INFO - fatal: The remote end hung up unexpectedlyġ786772 ( 12:19:00,693) WARN sg.command.ping - 'C:/Program Files (x86)/Git/INIT/' does not appear to be a git repository The version of SmartGit is 3.0.4, however the issue was also present in 2.x. I'm not sure why SmartGit doesn't place nice with this setup, but I reckon the default WinSSH settings are being bypassed by its SSH client, since its specifying the whole path completely from ' C:\Program Files (x86)\Git'.Īny ideas where SmartGit might be getting the ' C:\Program Files (x86)\Git' path from? It should be looking for it in ' C:\Git', not ' C:\Program Files (x86)\Git'. When I get SmartGit (using SmartGit SSH Client) to connect to the same server, with url: ssh://// When I use Git Bash to connect to the server, it defaults to ' C:\Git'. I've configured WinSSH to make all SSH sessions default to ' C:\Git' as their home folder, which works a treat. One curve-ball for us, is that although Git is installed at ' C:\Program Files (x86)\Git' our actual source code sits at ' C:\Git', which is backed up regularly. It hooks into AD to resolve usernames etc, and I've imported all the public RSA keys etc. I've got a source control server set up on the network, running MSYSGit with WinSSH as the SSH server. Modern hosted git solutions like Bitbucket support SSH key authentication.I'm wondering if anyone can shed some insight into why SmartGit isn't behaving when I'm connecting to our source control server through SSH. Git is capable of using SSH keys instead of traditional password authentication when pushing or pulling to remote repositories. Following this guide, you will be able to create and start using an SSH key. SSH keys are used to authenticate secure connections. If a linux subsystem is available the same steps previously discussed for Linux and Mac can be followed with in the windows linux subsystem. The windows linux subsystem offers a full linux shell within a traditional windows environment. Modern windows environments offer a windows linux subsystem. Once Git Bash is installed the same steps for Linux and Mac can be followed within the Git Bash shell. ![]() The most straight forward option is to utilize Git Bash. External shell programs will need to be installed for to have a complete keygen experience. Windows environments do not have a standard default unix shell. The new SSH key is now registered and ready to use! Generate an SSH Key on Windows ![]() execute the following to begin the key creation The process for creating an SSH key is the same between them.ġ. Generate an SSH Key on Mac and Linuxīoth OsX and Linux operating systems have comprehensive modern terminal applications that ship with the SSH suite installed. Most git hosting providers offer guides on how to create an SSH Key. The SSH command line tool suite includes a keygen tool. SSH keys are created using a key generation tool. This is a one-way formula that ensures the public key can be derived from the private key but the private key cannot be derived from the public key. At a very high level SSH keys are generated through a mathematical formula that takes 2 prime numbers and a random seed variable to output the public and private key. SSH keys are generated through a public key cryptographic algorithm, the most common being RSA or DSA. This data is then opened with the 'private' key which you hold in a secure place. You give the public 'lock' to remote parties to encrypt or 'lock' data. It is more helpful to think of the public key as a "lock" and the private key as the "key". The private vs public nomenclature can be confusing as they are both called keys. The key pair contains a public and private key. SSH uses a pair of keys to initiate a secure handshake between remote parties. The SSH acronym is also used to describe a set of tools used to interact with the SSH protocol. SSH is used for remote file transfer, network management, and remote operating system access. This authenticated and encrypted secure network protocol is used for remote communication between machines on an unsecured open network. An SSH key is an access credential for the SSH (secure shell) network protocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |