This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
policies:security:remoteaccess [2018/01/05 12:10] – external edit 127.0.0.1 | policies:security:remoteaccess [2018/01/15 16:40] (current) – deul | ||
---|---|---|---|
Line 1: | Line 1: | ||
======Remote access====== | ======Remote access====== | ||
- | For the purpose of working outside the institute, access to the local systems is provided in several secure ways: | + | {{ : |
* **Remote login**: There are ssh servers tha provide login facilities to the institute front end computers. These ssh servers can be used to further login to local Linux desktops and servers or can be used to build ssh tunnels to allow remote access to local facilities, such as desktop graphical interface or license server. | * **Remote login**: There are ssh servers tha provide login facilities to the institute front end computers. These ssh servers can be used to further login to local Linux desktops and servers or can be used to build ssh tunnels to allow remote access to local facilities, such as desktop graphical interface or license server. | ||
* **Desktop access**: Using an ssh tunnel the graphical interface of a Linux desktop/ | * **Desktop access**: Using an ssh tunnel the graphical interface of a Linux desktop/ | ||
* **License access**: Using an ssh tunnel a remote machine running a licensed package can obtain a license key from the institute license pool, thus running licensed software as if inside the institue. | * **License access**: Using an ssh tunnel a remote machine running a licensed package can obtain a license key from the institute license pool, thus running licensed software as if inside the institue. | ||
* **VPN**: It is also possible to run a vpn client (after having obtained certifications keys from system management), | * **VPN**: It is also possible to run a vpn client (after having obtained certifications keys from system management), |