Computer Documentation Wiki

User Tools

Site Tools

Trace: • fedora_27 • web • rdp_mac • sudo • classification • laptop_connectivity • matlab_ullicense • 2fa-key • fedora_25 • fedora_31
policies:security:remoteaccess

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
policies:security:remoteaccess [2018/01/15 16:40] – deulpolicies:security:remoteaccess [2018/01/15 16:40] (current) – deul
Line 1: Line 1:
 ======Remote access====== ======Remote access======
-{{ :policies:security:terminal-icon-md.png?200|}}For the purpose of working outside the institute, access to the local systems is provided in several secure ways:+{{ :policies:security:terminal-icon-md.png?100|}}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/server of Windows desktop can be forwarded to the remote requester that has authenticated him/herself through the ssh login. This way one can fully take over the desktop in user space.   * **Desktop access**: Using an ssh tunnel the graphical interface of a Linux desktop/server of Windows desktop can be forwarded to the remote requester that has authenticated him/herself through the ssh login. This way one can fully take over the desktop in user space.
   * **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), thus becoming part of local institute domain. This is particularly useful when accessing IP restricted information, such as library resources.   * **VPN**: It is also possible to run a vpn client (after having obtained certifications keys from system management), thus becoming part of local institute domain. This is particularly useful when accessing IP restricted information, such as library resources.
policies/security/remoteaccess.1516034419.txt.gz · Last modified: by deul

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki