Skip to Content
Last modified by Alexandru Pentilescu on 2024/07/16 22:44
From version 7.1
edited by Alexandru Pentilescu
on 2024/07/16 21:34
Change comment: There is no comment for this version
To version 9.1
edited by Alexandru Pentilescu
on 2024/07/16 21:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -154,11 +154,11 @@
154 154  If you need more configuration information, check [[this>>https://docs.gitea.com/administration/config-cheat-sheet]] out.
155 155  
156 156  = Activating SSH passthrough =
157 +
157 157  This is the most complex step out of all of them. In order to take advantage of the fact that SSH git pulls/pushes will be done via standard port 22, normal SSH traffic needs to be differentiated from git specific SSH traffic.
158 158  
159 159  To this end, multiple configurations will need to be done.
160 160  
161 -== Enable SSH login for the git user ==
162 162  This one's extremely important. Failing to perform this step will make SSH git pulls and pushes require to be done directly from the 2200 port like so
163 163  
164 164  {{code language="bash"}}
... ... @@ -167,6 +167,8 @@
167 167  
168 168  While this isn't the end of the world, ideally, all SSH traffic should be routed to port 22, as is standard. VPS firewalls or intermediary ISPs may, themselves, block off incoming or outgoing traffic to unconventional ports, which can cause issues. As such, using the standard port 22 for SSH communication would be ideal.
169 169  
170 +== Enable SSH login for the git user ==
171 +
170 170  So, to enable SSH capabilities to the git user, please edit the "/etc/ssh/sshd_config" configuration and change the following line:
171 171  
172 172  {{code language="text"}}
... ... @@ -178,3 +178,11 @@
178 178  {{code language="bash"}}
179 179  systemctl restart ssh
180 180  {{/code}}
183 +
184 +== Generate a proper public/private keypair for all the accounts that need to use git via SSH with ==
185 +
186 +This part's pretty self explanatory.
187 +
188 +For each user, on each device, that will require SSH git access to the aforementioned git server, they will need to have their own public/private authentication keypair set under a Gitea user that's already registered on the Gitea web portal.
189 +
190 +