#Git tortoisehg ssh how to#
#Git tortoisehg ssh update#
#Git tortoisehg ssh code#

Therefore, we only accept connections which are encrypted with HTTPS to the repositories and do backups regularly. That means that the data on the servers are subject to German data protection regulations and laws.įurthermore, we do our utmost to ensure our service‘s security.

#Git tortoisehg ssh code#

The question arises is your source code safe at Versionshelf?įact is that Versionshelf hosts only on servers in Germany. The current debate on Prism and the monitoring of the inernet does not leave Versionshelf entirely unaffected.

Secure hosted version control - Wolfgang.

for IE 6) over a secure up-to-date configuration.

We are taking security really serious, and we will never choose backwards compability (e.g. This means no weak RC4-Cipher usage, no unsecure DiffiHellmann key-exchange support and not vulnerable against Poodle, Heartbleed or Beast attacks. We are still reaching the Overall Rating A at the test. Last week we renewed our SSL certificate for to keep your connections with the Versionshelf servers secure and encrypted.Ī quick look at the popular and free SSL Labs from Qualys shows what SSL configuration hardening should look like.

#Git tortoisehg ssh update#

SSL certificate update - Class A rating - Wolfgang.

With this you always exactly know who can read, write or has no permissions to access the repository at all. You don’t have to assign permissions to each user, but can simply assign users to a team and configure rights for that team.Īdditionally we now show the effective user permissions. Like users, also teams can get granular permissions on a repository level.įor admins the permissions configuration gets much easier. More on this shortly.įrom now on Versionshelf supports teams.

#Git tortoisehg ssh how to#

There we describe how to use ssh keys, how to clone your repository and also display the repository specific ssh url.Īlso ssh access for git repositories is on its way. Please find the details how to access your repository via ssh in the Versionshelf admin under the repository details. Just create a special deployment user, supply the public ssh key and trigger deployments with a Versionshelf web hook call. Installation of the mercurial_keyring extension or - even worse - the use of insecure plain text passwords in your hgrc configuration is not necessary anymore.Īnother great use for ssh keys is automated project deployments. Slack Integration works for git, mercurial and subversion repositories.įinally SSH access to mercurial repositories has landed! Just add your public ssh key to your Versionshelf account and you can clone, push and pull via Secure Shell (SSH) to your mercurial repositories.īesides beeing a secure transport mechanism, SSH access allows all operations without using a login or password. To activate Slack Integration create an Incoming WebHook on Slack (Account Settings -> Configure Apps -> Custom Integrations) and copy the url to your Versionshelf repository Slack configuration. This gives you quick access to the details of each commit. Now up to five commit revision ids get displayed and conveniently linked to the versionshelf revision browser view. Until now we only sent messages about a push, but not the individual commits. Versionshelf integration for Slack helps you to keep track of your teams repository activities. For quite some time we have Slack integration implemented.