Hi Karel, welcome to the Community.
To access a repo via SSH you need to set SSH keys. Using a separate password wouldn't be possible and it would defeat the purpose of SSH:
When you set up SSH, you create a key pair that contains a private key (saved to your local computer) and a public key (uploaded to Bitbucket). Bitbucket uses the key pair to authenticate anything the associated account can access. This two-way mechanism prevents man-in-the-middle attacks.
For more information you can read Set up an SSH key.
If you'd prefer to enter your password with every interaction, is there a reason why you wouldn't use HTTPS? You can find a comparison at SSH keys.
Let us know,
I understand the reason for SSH and keys. However, I spent a whole day on Sunday fighting my Synology NAS box with using keys. For some reason, it is rejecting the private Key. I'm frustrated with this mess and would just like to update my repo. That's why I wanted to use it as a backup my username and password. I was using Putty to generate the keys.
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event