This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
institute_lorentz:institutelorentz_remoteaccess [2022/05/31 09:03] – lenocil | institute_lorentz:institutelorentz_remoteaccess [2022/11/29 12:27] (current) – [SSH access/tunnelling behind firewalls] lenocil | ||
---|---|---|---|
Line 98: | Line 98: | ||
<code bash> | <code bash> | ||
Host ssh.lorentz.firewall | Host ssh.lorentz.firewall | ||
- | ProxyCommand openssl s_client -connect access.lorentz.leidenuniv.nl: | + | ProxyCommand openssl s_client -connect access.lorentz.leidenuniv.nl: |
User <Your IL username> | User <Your IL username> | ||
</ | </ | ||
Line 135: | Line 135: | ||
When the connection is initiated you will be able to double-check the SSL certificate details, especially the '' | When the connection is initiated you will be able to double-check the SSL certificate details, especially the '' | ||
- | Similarly it is possible to initiate an SSL-wrapped SSH SOCKS proxy connection as in the example below | + | Similarly it is possible to initiate an SSL-wrapped SSH SOCKS proxy connection |
+ | |||
+ | <code bash> | ||
+ | ssh -ND 8888 ssh.lorentz.firewall | ||
+ | </ | ||
+ | |||
+ | then modify your browser settings to instruct it to redirect all connections to a SOCKS proxy listening on '' | ||