Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,673
Community Members
 
Community Events
176
Community Groups

Bug in SourceTree-created SSH configuration for GitLab Enterprise

I just used the key generation features in the Accounts dialog to generate a key and modify my SSH configuration for a GitLab Enterprise account. Unfortunately, SourceTree 4.1.8 (on Mac OS Monterey) put buggy configuration in my ~/.ssh/config file, as follows. Note that all of these bugs appear to be related to the space in "GitLab Enterprise".

  • The `HostName` line contained `GitLab Enterprise` instead of the actual name of my GitLab host. This is both a syntax error (the hostname can't contain spaces) and incorrect.
  • The key file created by SourceTree was called "GitLab Enterprise". That's fine, but the relevant line in the SSH config file said `IdentityFile /Users/marnen/.ssh/marnen-GitLab Enterprise`. The space is a syntax error, and I had to put double quotes around the filename to get it to work.
  • The `Host` line in the SSH config file says `Host marnen-GitLab Enterprise`. That's not a syntax error, but I don't think it's correct; that line is supposed to contain multiple space-separated patterns.

As mentioned above, I suspect that all these problems arise from SourceTree not handling the space in "GitLab Enterprise" correctly when writing the SSH config file. Please fix this.

2 comments

Same annoying issue with gitlab enterprise not being properly configured

Same issue for me. Please fix!

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events