Skip to Content

Changes for page SSH tunnel

Last modified by Jan Rhebergen on 2023/01/04 15:57
From version 4.1
edited by Jan Rhebergen
on 2022/12/29 21:55
Change comment: There is no comment for this version
To version 1.3
edited by Jan Rhebergen
on 2022/12/29 13:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -91,12 +91,9 @@
91 91  This should generate some output on the restricted client due to the ##-vvv## option we supplied. When this indeed is the case just quit and commence with the following actual test.
92 92  
93 93  (% class="box" %)
94 -{{{ssh -p 8082 localhost
95 -#JBR or alternatively for instance:
96 -ssh -p 8082 jan@localhost
97 -}}}
94 +{{{ssh -p 8082 localhost}}}
98 98  
99 -This should log you in on the restricted host. If you need to supply a password it means you did not copy your own public keys or the permission of the ##authorized_keys## file in set incorrectly. These keys are different (personal) public keys that you should have on your home pc/laptop account. Again this should generate respective verbose output on the restricted host. When succesful you can logout on the middle man host and also stop the ##autossh## running on the restricted host. If you cannot login from an outside host (not localhost) it might be because the provider that hosts your middle man server has a firewall that need to be adjusted (i.e. amazon, oracle, etc).
96 +This should log you in on the restricted host. If you need to supply a password it means you did not copy your own public keys or the permission of the ##authorized_keys## file in set incorrectly. These keys are different (personal) public keys that you should have on your home pc/laptop account. Again this should generate respective verbose output on the restricted host. When succesful you can logout on the middle man host and also stop the ##autossh## running on the restricted host.
100 100  
101 101  == Automation and persistence ==
102 102