<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="de">
	<id>https://www.kruedewagen.de/w/index.php?action=history&amp;feed=atom&amp;title=Git%2FSSH_Authentifizierung</id>
	<title>Git/SSH Authentifizierung - Versionsgeschichte</title>
	<link rel="self" type="application/atom+xml" href="https://www.kruedewagen.de/w/index.php?action=history&amp;feed=atom&amp;title=Git%2FSSH_Authentifizierung"/>
	<link rel="alternate" type="text/html" href="https://www.kruedewagen.de/w/index.php?title=Git/SSH_Authentifizierung&amp;action=history"/>
	<updated>2026-05-03T01:13:22Z</updated>
	<subtitle>Versionsgeschichte dieser Seite in www.kruedewagen.de</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://www.kruedewagen.de/w/index.php?title=Git/SSH_Authentifizierung&amp;diff=9144&amp;oldid=prev</id>
		<title>Rkr: Die Seite wurde neu angelegt: „Git repository servers behave different in terms of SSH authentication. This depends on the way SSH is implemented, e.g. by using the standard OpenSSH client/s…“</title>
		<link rel="alternate" type="text/html" href="https://www.kruedewagen.de/w/index.php?title=Git/SSH_Authentifizierung&amp;diff=9144&amp;oldid=prev"/>
		<updated>2015-07-15T07:02:35Z</updated>

		<summary type="html">&lt;p&gt;Die Seite wurde neu angelegt: „Git repository servers behave different in terms of SSH authentication. This depends on the way SSH is implemented, e.g. by using the standard OpenSSH client/s…“&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Neue Seite&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Git repository servers behave different in terms of SSH authentication. This depends on the way SSH is implemented, e.g. by using the standard OpenSSH client/server, an own SSH implementation or a wrapper around it.&lt;br /&gt;
&lt;br /&gt;
A) Gerrit&lt;br /&gt;
&lt;br /&gt;
Gerrit has its own Git-only SSH server. You login with your individual Gerrit username on a separate port (e.g. 29418) and you need a SSH public key registered in your profile ([https://gerrit-review.googlesource.com/Documentation/user-upload.html#ssh at least for pushes]). I guess that read operations also work without SSH key. However, the SSH username is different for each user.&lt;br /&gt;
&lt;br /&gt;
B) GitLab&lt;br /&gt;
&lt;br /&gt;
GitLab (which is my preferred Git repo server) implements a gitlab-shell, which is a wrapper for SSH. All users typically login via ssh://git@server/group/project on standard SSH port 22. So, all users use one and the same git user within the SSH path. Before you can login, you need to [http://doc.gitlab.com/ce/ssh/README.html add a SSH public key] (or more) into your GitLab profile. The GitLab backend now checks the &amp;quot;incoming&amp;quot; SSH key towards all registered public keys and will automatically link your session to your profile. Note: Therefore, one and the same public SSH key can only be assigned to one profile.&lt;br /&gt;
&lt;br /&gt;
C) Gitolite&lt;br /&gt;
&lt;br /&gt;
I guess that Gitolite works similar to GitLab by using only one SSH user name and different SSH keys to authenticate and to link to your profile. See [http://gitolite.com/gitolite/glssh.html how gitolite uses ssh].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Kategorie:Git]]&lt;/div&gt;</summary>
		<author><name>Rkr</name></author>
	</entry>
</feed>