Last modified by Alexandru Pentilescu on 2024/07/16 22:44

From version 6.1
edited by Alexandru Pentilescu
on 2024/07/16 21:25
Change comment: There is no comment for this version
To version 8.1
edited by Alexandru Pentilescu
on 2024/07/16 21:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -152,3 +152,29 @@
152 152  {{/code}}
153 153  
154 154  If you need more configuration information, check [[this>>https://docs.gitea.com/administration/config-cheat-sheet]] out.
155 +
156 += Activating SSH passthrough =
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 +
159 +To this end, multiple configurations will need to be done.
160 +
161 +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
162 +
163 +{{code language="bash"}}
164 +git clone ssh://git@transistor.one:2200/Alex/Licenta.git
165 +{{/code}}
166 +
167 +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.
168 +
169 +== Enable SSH login for the git user ==
170 +So, to enable SSH capabilities to the git user, please edit the "/etc/ssh/sshd_config" configuration and change the following line:
171 +
172 +{{code language="text"}}
173 +AllowUsers alex git
174 +{{/code}}
175 +
176 +Obviously the "alex" user doesn't need to be here. The git user does. Change this list as best suits your needs. Don't forget to restart the service after you're done:
177 +
178 +{{code language="bash"}}
179 +systemctl restart ssh
180 +{{/code}}