Generating A Ssh Key Pair In Sourcetree For Bitbucket

• Generating A Ssh Key Pair In Sourcetree For Bitbucket Windows 10
• Generating A Ssh Key Pair In Sourcetree For Bitbucket 2

• Status:Closed(View Workflow)
• Resolution: Fixed
• Fix Version/s: None
• Labels:
• Environment:

  Mac OS X Sierra desktop

  Bitbucket Server

  Sourcetree 2.4 (and the Beta has this problem too)

• Aug 01, 2015  BitBucket - Set up SSH key pair for Git. This short video shows how you can create a public/private SSH key pair and register your public key with BitBucket. (Bitbucket) + SourceTree GUI.
• Hi, i am new to pipelines and able to generate ssh key pair under pipelines setting and also added to my remote host. Luckily when adding host name and by clicking on.

Don't use PuTTY to generate the key. Create a new key with ssh-keygen in.ssh. Leave passwords blank. Open that new key in PuTTY. Copy and paste it into the Bitbucket Key field. Save key with PuTTY and Bitbucket. It should work.

Please watch my short video illustrating the experience.
https://www.youtube.com/watch?v=wPUAkG78BFE&feature=youtu.be

Scenario 1:

On MacOS X Sierra when setting up SourceTree for first time and choosing 'SSH' as the authentication method, SourceTree:

1. Should not have a URL for the Bitbucket server, should be a hostname without the https://
2. Should not need a 'password'
3. Generate SSH Key button is greyed out
4. User can skip setup and perform this step manually through the Remote Repository Browser's 'Add Account' function

Scenario 2

On MacOS X Sierra when using the 'Add Account' function the experience when selecting SSH as the authentication method is:

1. URL is asked for, should be a hostname
2. Password is not needed
3. User should be able to select an existing ssh key on their system
4. Generate Key button is visible and clickable, when clicked, process continues, but no key is generated and a 'Tooltip' is displayed when account is saved indicating no SSH key
5. When editing the account, and selecting 'Generate Key' it now works (but generates a public/private key with a 'space' in the filename (e.g. mwilde_Bitbucket Server.pub)

After putting my public key in my account on Bitbucket and trying to clone, errors are related to what is in the '.ssh/config' file this occurs.

In addition, I have given the keypair a special name that can be used to select it in diverse applications. yes/no: yesThen try generating a new RSA keypair anew:configure terminalcrypto key generate rsa label ssh modulus 1024The name for the keys will be: ssh% The key modulus size is 1024 bits% Generating 1024 bit RSA keys, keys will be non-exportable.OK (elapsed time was 3 seconds)This alone should make sure that the SSH is able to run in SSHv2. Perhaps you have several RSA keypairs configured, and the SSH is using some short keypair that does not allow running SSHv2.I suggest erasing all existing RSA keypairs using the crypto key zeroize rsa as follows:configure terminalcrypto key zeroize rsa% All RSA keys will be removed.% All router certs issued using these keys will also be removed.Do you really want to remove these keys? Cisco router generate rsa key 1024 number. Hmm, this is an interesting issue.

1. No hostname is in the '.ssh/config' file (edited by SourceTree) causing a failure on clone
2. When hostname is added, errors occur due to 'space' in filename
3. When '.ssh/config' is edited removing spaces and subsequently renaming the private key to match the reference in the '.ssh/config' file

After 'fixing' all of these issues, cloning only works thru the CLI, or via a 'Clone in SourceTree' link up in Bitbucket Server. Cloning does not work through the remote repository browser.

Please watch my short video illustrating the experience.
https://www.youtube.com/watch?v=wPUAkG78BFE&feature=youtu.be

Note: I have a few hundred people in my company i'd like to train on SourceTree (and have them use SSH keys if possible), so please fix this ASAP.

Assignee:

Brian Ganninger (Inactive)

Reporter:

Michael S Wilde

Votes:

0Vote for this issue

Watchers:

2Start watching this issue

Before you continue, make sure to sign in.

Once you login, you will see a list of all users (which will initially be empty). In the upper right corner click on the user plus button (Fig-1).
Fig-1

Configure New User

Fig-2

Refer to Fig-2:1. Username is required and must be unique.

1. SSH Key Details is used to login to SFTP Gateway instead of a password.
   Select one of these options for the user * The 'Generate new SSH keys pair' option will generate a new key pair, write the public key to the authorized_keys file, and download the private key once the user is saved.

   Note: You will need to make the private key available to the user by email or any other secure way (learn more).

• The 'Upload user-provided SSH key' option will display a browse button that will allow you to navigate to a public key file to be uploaded and written to the user's authorized_keys file.

1. S3 Encryption Level is used to encrypt object uploaded to S3 by the user.
   Here are all your options: * SSE-S3: Is used by default. There is no additional cost, performance impact, nor key management overhead. You basically get some security compliance with no drawbacks. * KMS: You use the AWS key-managed service for encryption. This is similar to SSE-S3, but requires some configuration on your part. If you are not seeing the KMS keys you created, click the refresh button next to the dropdown. * No server side encryption: This is a good option if your S3 bucket is open to the public. Otherwise, it's best to take advantage of SSE-S3.

2. Enable Shared Directory is used to allow multiple SFTP Gateway users to access the same set of files. This will create a folder in the default S3 bucket (even if the user has a custom bucket configured) called /shared.
   Any files created in this S3 location will get synced down to this Linux filesystem location: /home/username/home/username/shared/

3. Enable Download Directory is used to allow this user to see what is on S3 through the use of Download Folders.
   By default, this will create a folder in your S3 bucket: /downloads. Any files created in this S3 location will get synced down to this Linux filesystem location:
   /home/username/home/username/downloads/

4. Upload Destination S3 Bucket Name is used to specify the custom S3 bucket name for this user.

Note: This will create a new bucket or point to an existing bucket that you own.

Generating A Ssh Key Pair In Sourcetree For Bitbucket Windows 10

1. Upload Destination Prefix is used to specify the S3 path to use for this user.

Note: The user's files will be uploaded to s3://my-custom-bucket/my/custom/path/.

Generating A Ssh Key Pair In Sourcetree For Bitbucket 2

Updated