{"id":6063,"date":"2020-11-18T20:08:58","date_gmt":"2020-11-18T20:08:58","guid":{"rendered":"https:\/\/research.reading.ac.uk\/act\/?post_type=kbe_knowledgebase&#038;p=6063"},"modified":"2021-05-05T18:39:07","modified_gmt":"2021-05-05T17:39:07","slug":"arc-ssh","status":"publish","type":"kbe_knowledgebase","link":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/","title":{"rendered":"Externally visible ssh server &#8211; arc-ssh"},"content":{"rendered":"<p><b><span data-contrast=\"auto\">arc-ssh.reading.ac.uk<\/span><\/b> <span data-contrast=\"auto\">is an externally visible ssh server. It exists to allow access to the UoR network and Linux-related resources from off-campus. Typical applications include accessing the <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase_category\/cluster\/\">Reading Academic Research Cluster (RACC)<\/a>, copying data using tools like sftp, scp or rsync, and secure access to other campus services via tunneled SOCKS proxy or port mapping.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b><span data-contrast=\"auto\">In this article, you will find key instructions on how to:<\/span><\/b><\/h4>\n<ul>\n<li><span data-contrast=\"auto\">Section 1: Check if you need to apply for access.<\/span><\/li>\n<li>Section 2: Login to arc-ssh using a one-time code emailed to your UoR email address.<\/li>\n<li><span data-contrast=\"auto\">Section 3: Set up your ssh key pair (optional,<\/span><span data-contrast=\"auto\">\u00a0but recommended for experienced users<\/span><span data-contrast=\"auto\">).<\/span><\/li>\n<li><span data-contrast=\"auto\">Section 4: Set up your authenticator app (optional, but recommended for experienced users).<\/span><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h1><span data-contrast=\"none\">1. Check if you need to apply for access<\/span><\/h1>\n<p><span data-contrast=\"auto\">To access arc-ssh you will need to use an ssh client, such as e.g. MobaXterm, a Mac or Linux Terminal or similar. The following ssh command is used to log in to arc-ssh, substituting &lt;UoR login&gt; with your username.\u00a0<\/span><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh &lt;UoR login&gt;@arc-ssh.reading.ac.uk<\/pre>\n<p><span data-contrast=\"auto\"> If you are not registered to use arc-ssh you will not be granted access when you attempt to login from off-campus. After you enter your UoR password into arc-ssh and it is verified, if you are not registered to use the service you will see a message like\u00a0 the following example:<\/span><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh &lt;UoR login&gt;@arc-ssh.reading.ac.uk\u00a0\r\nPassword:\u00a0\u00a0\r\n&lt;UoR login&gt; not registered to use this service<\/pre>\n<p><span data-contrast=\"auto\">If that happens you need to raise a ticket to DTS and you be added to the group arc-remote-users group (for all Linux ARC remote access services, unless there is a specific requirement access is limited to arc-ssh). You should only use your UoR email address or the self-service portal to apply for access, so that we can confirm that the request comes from you. In some cases further checks that the request is genuine might be needed.\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">When connecting from the UoR campus network, you will be allowed to login to arc-ssh without registering.<\/span><span data-contrast=\"auto\">\u00a0<\/span><\/p>\n<p>&nbsp;<\/p>\n<h1><span data-contrast=\"none\"> 2. Login using one-time email codes<\/span><\/h1>\n<p><span data-contrast=\"auto\">Assuming you did not yet set up <\/span>Google Authenticator or ssh keys (see below)<b><span data-contrast=\"auto\">, after you successfully authenticate with your UoR password, you will be prompted to enter a one-time email code, like in the following example:<\/span><\/b><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh &lt;UoR login&gt;@arc-ssh.reading.ac.uk -X\u00a0\r\nPassword: \u00a0\r\nThe code received by email (timestamp 20:37:57):\u00a0\r\n\r\n[&lt;UoR login&gt;@arc-ssh ~]$<\/pre>\n<p><span data-contrast=\"auto\">You just need to copy and paste the 6 digit code you find in the email that has just been sent to your UoR email account. Note that the code is valid only for this particular email code authentication prompt and that it times out eventually. The timestamp can help to ensure that you use the right code. It makes sense to have your email client already opened and be ready to copy the code. If you do not manage to enter the email code in time, the session will time out. You will need to enter the UoR password again, you will receive another email with a new code, and you will be expected to enter this new code.<\/span><\/p>\n<p><span data-contrast=\"auto\">Note that on a Linux you might not get asterisks (*) printed when you type the password or the email code.\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">New users of UoR Linux systems can stop here and just use the email codes to login to arc-ssh. However, we recommend that all users, once they have some experience in using our systems, set up a more robust second-factor authentication. The following two methods of authentication will replace the email code authentication. If you set up Google Authenticator, it will disable the email codes. SSH keys can be used in addition to either the email codes or Google Authenticator. When a correct ssh key is present, you will not be asked for an email code or verification code, but you still will be able to use an email code or Google verification code if you do not have the right private key on the client device, e.g. when you use a different computer to connect, not the one on which you have stored the ssh key.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h1><span data-contrast=\"none\"> 3. Set up your ssh key pair<\/span><\/h1>\n<p><b><span data-contrast=\"auto\">Setting up ssh key authentication allows to automate the second part of the login process. It can be used e.g. on your home machine, while you still will be able to login using one time codes, either sent by email or generated by Google Authenticator, when connecting from other machines.<\/span><\/b><span data-contrast=\"auto\"> You need to generate an ssh key pair on your local machine and place the public key in your .ssh\/authorized_keys file in your UoR Unix home directory. Below are short instructions that are not specific to any particular operating system and ssh client. We repeat these steps in the more detailed instructions for <\/span><a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/act-ssh-with-mobaxterm-step-by-step-guide\/\"><span data-contrast=\"auto\">MobaXterm<\/span><\/a><span data-contrast=\"auto\"> users (with videos) and for <\/span><a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/act-ssh-for-linux-and-mac-users-step-by-step-guide\/\"><span data-contrast=\"auto\">Linux or Mac users.<\/span><\/a><\/p>\n<p><span data-contrast=\"auto\">Let&#8217;s generate the ssh key first. When we run the following command, we will use the default file name and we will not set the passphrase her<\/span><span data-contrast=\"auto\">e (because we use two factor authentication anyway). The<\/span><span data-contrast=\"auto\"> ssh key pair is generated simply with:<\/span><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh-keygen<\/pre>\n<p><span data-contrast=\"auto\">This generates a private (for your machine) and a public key (for the remote machine). In order to use those keys to authenticate, the public key has to be copied from your machine to arc-ssh. The easiest way to do that is by<\/span><span data-contrast=\"auto\">\u00a0using the ssh-copy-id command below. <\/span><span data-contrast=\"auto\">We recommend that you use this method as it automatically adds your public key to the right file and, if needed, it corrects the relevant directory and file permissions as required. <\/span><span data-contrast=\"auto\">When running this command you will need to connect to arc-ssh, and you will need to login with two factor authentication. As this login cannot be not be authenticated with your new ssh key yet, it will be authenticated either with an email code (like in section 2) or with Google Authenticator verification code if you set this up already (see section 4). <\/span><b><span data-contrast=\"auto\">Note that if you specify a non-standard name for your private key, you will need to explicitly provide this name <\/span><\/b><b><span data-contrast=\"auto\">with the ssh-copy-id command\u00a0<\/span><\/b><b><span data-contrast=\"auto\"> (and later <\/span><\/b><b><span data-contrast=\"auto\">with the ssh command <\/span><\/b><b><span data-contrast=\"auto\">as well). This is only recommended for experienced linux users who are familiar with ssh keys.\u00a0<\/span><\/b><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh-copy-id &lt;UoR login&gt;@arc-ssh.reading.ac.uk\u00a0\r\nPassword:\u00a0\r\nThe code received by email (timestamp xx:xx:xx):<\/pre>\n<p><span data-contrast=\"auto\">Once the public key (matching with the private key stored on your device) is transferred to arc-ssh, ssh key authentication will replacethe one time code authentication:<\/span><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh &lt;UoR user name&gt;@arc-ssh.reading.ac.uk -X\u00a0\r\nPassword:\u00a0\r\nAuthenticated with public key.\u00a0\r\n[&lt;UoR login&gt;@arc-ssh ~]$<\/pre>\n<p>&nbsp;<\/p>\n<h1><span data-contrast=\"none\">4. Set up Google Authenticator<\/span><\/h1>\n<p><span data-contrast=\"auto\">Once Google Authenticator is configured, by running the setup script below on arc-ssh, prompting for the Google Authenticator verification code will replace prompting for and sending email codes. <strong>We recommend to replace email codes with Google Authenticator codes<\/strong> because email is not a reliable way to deliver the authentication code on time. There is a risk you might not be able to login when there is some delay with your email delivery. (Note that using ssh key as shown in the previous section is also a good way to make sure you do not rely on the email codes when you connect from a trusted machine).<\/span><\/p>\n<p><span data-contrast=\"auto\">The general idea of Google Authenticator is as follows: A secret key is placed in a file on the server. On the ACT systems using this method of authentication the file is located at \/var\/authenticator\/&lt;UoR username&gt;\/.google_authenticator. The secret key is also transferred to your mobile device when you scan the QR code (you can also achieve this by copying the secret key by hand, or by using the URL to have the QR code displayed in a web browser), and it is stored in the authenticator app. The secret key plus the current time is used to generate time based verification codes. Comparing those verification codes confirms the identity of the device used to authenticate the connection.<\/span><\/p>\n<p><span data-contrast=\"auto\">You need to install the <\/span><b><span data-contrast=\"auto\">Microsoft Authenticator<\/span><\/b><span data-contrast=\"auto\"> app (this is recommended because it is already used with other UoR services) or the <\/span><b><span data-contrast=\"auto\">Google Authenticator<\/span><\/b><span data-contrast=\"auto\"> app on your phone. Both the Google and Microsoft apps are compatible with the Google Authenticator service and the following setup steps are the same in both cases. Once the app is installed, <\/span><b><span data-contrast=\"auto\">run the configuration script below on arc-ssh<\/span><\/b><span data-contrast=\"auto\">. The script will produce a QR code that allows to transfer the secret to your mobile device without having to copy the long code manually. In the app, you will need to <\/span><b><span data-contrast=\"auto\">scan the QR code displayed on the computer screen<\/span><\/b><span data-contrast=\"auto\">. <\/span><b><span data-contrast=\"auto\">If you have problems with the QR code displayed in the text console, you can use the provided URL, or you can copy the secret key as text.<\/span><\/b><span data-contrast=\"auto\"> The configuration script is modified to store the Authenticator files locally on arc-ssh, not in your shared home directory, so that setting it up on arc-ssh will not affect how you login to other UoR services. Note that every time you run the script, a new secret code is created and the old one is overwritten. That means that each time you run the script, you need to scan the QR code again.\u00a0\u00a0\u00a0<\/span><\/p>\n<p><span data-contrast=\"auto\">In the following example, we first login to arc-ssh using the email code (see section 2) as the second authentication method. Once we are connected to arc-ssh, we run the script which replaces the email codes with Google Authenticator.\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh &lt;UoR login&gt;@arc-ssh.reading.ac.uk -X\u00a0\r\nPassword:\u00a0\r\nThe code received by email (timestamp xx:xx:xx):\u00a0\u00a0\u00a0\r\n\r\n[&lt;UoR login&gt;@arc-ssh ~]$ google-authenticator\u00a0\u00a0\r\nWarning: pasting the following URL into your browser exposes the OTP secret to Google:\u00a0\r\nhttps:\/\/www.google.com\/chart?chs=200x200&amp;chld=M|0&amp;cht=qr&amp;chl=otpauth:\/\/totp\/qx901702@arc-ssh.reading.ac.uk%3Fsecret%3D27DEDDS2OPLD7LBL3KKU2ZPIKQ%26issuer%3Darc-ssh.reading.ac.uk<\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-6066 colorbox-6063\" src=\"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/2020\/11\/GetImage.png\" alt=\"\" width=\"200\" height=\"200\" srcset=\"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/2020\/11\/GetImage.png 200w, https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/2020\/11\/GetImage-150x150.png 150w\" sizes=\"auto, (max-width: 200px) 100vw, 200px\" \/><\/p>\n<pre class=\"lang:default decode:true\">Your new secret key is: 27DEDDS2OPLD7LBL3KKU2ZPIKQ \r\nYour verification code for code 1 is 367461\u00a0\r\nYour emergency scratch codes are:\u00a0\r\n\u00a0 81427850\u00a0\r\n\u00a0 28709993\u00a0\r\n\u00a0 77729003\u00a0\r\n\u00a0 73219531\u00a0\r\n\u00a0 80982761\u00a0\r\n\r\n[&lt;UoR login&gt;@arc-ssh ~]$<\/pre>\n<p><span data-contrast=\"auto\">It makes sense to save a copy of the <\/span><span data-contrast=\"auto\">emergency\u00a0 <\/span><span data-contrast=\"auto\">scratch codes. You can use them in case you are not able to login with the standard, time based, verification codes.<\/span><\/p>\n<p><b><span data-contrast=\"auto\">The URL, the QR code and the secret key contains the same secret, they should not be revealed, printed or stored in a file.<\/span><\/b><span data-contrast=\"auto\"> I have removed my <\/span><span data-contrast=\"auto\">\/var\/authenticator\/qx901702\/.google_authenticator after running this example, such that this secret is not valid anymore.\u00a0<\/span><\/p>\n<p><span data-contrast=\"none\">Now, when you login, you will be prompted for the verification code from the app, not for the code sent by email:<\/span><\/p>\n<pre class=\"lang:default decode:true\">[janedoe@homepc] \u27a4 ssh &lt;UoR login&gt;@arc-ssh.reading.ac.uk -X\u00a0\r\nPassword:\u00a0\u00a0\r\nVerification code:\u00a0\r\n\u00a0\r\n[&lt;UoR login&gt;@arc-ssh ~]$<\/pre>\n<p><span data-contrast=\"auto\">In case you want to revert to using email codes, you will need to log in to arc-ssh and remove the file <\/span><span data-contrast=\"auto\"><span class=\"lang:default highlight:0 decode:true crayon-inline\">\/var\/authenticator\/&lt;UoR login&gt;\/.google_authenticator<\/span>.\u00a0<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><strong>Further information:<\/strong><\/h4>\n<ul>\n<li>For alternative off-campus connection options see: <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/connect-from-outside-of-campus\/\">Connect from outside of campus<\/a><\/li>\n<li>Further instructions related to arc-ssh can be found here: <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh-with-mobaxterm-step-by-step-guide\/\">arc-ssh with MobaXterm \u2013 step by step guide<\/a>, <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh-for-linux-and-mac-users-step-by-step-guide\/\">arc-ssh for Linux and Mac users &#8211; step by step guide<\/a>,<\/li>\n<li>Articles loosely related to the topic: <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/access-to-act-servers-via-an-ssh-client\/\">Access to ACT Servers via an SSH Client<\/a>, <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/transferring-research-data-to-and-from-uor-systems\/\">Research data transfer using act-ssh.reading.ac.uk<\/a>, <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/act-ssh-connection-caching-for-automated-data-transfers-from-unix\/\">act-ssh \u2013 connection caching for automated data transfers<\/a>, <a href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/connect-from-outside-of-campus\/\">Connect from outside of campus<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>arc-ssh.reading.ac.uk is an externally visible ssh server. It exists to allow access to the UoR network and Linux-related resources from off-campus. Typical applications include accessing the Reading Academic Research Cluster (RACC), copying data using tools like sftp, scp or rsync, and secure access to other campus services via tunneled SOCKS proxy or port mapping. <\/p>\n","protected":false},"author":364,"featured_media":5701,"template":"","meta":{"_acf_changed":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"__cvm_playback_settings":[],"__cvm_video_id":"","_links_to":"","_links_to_target":""},"kbe_taxonomy":[61,80],"kbe_tags":[],"class_list":["post-6063","kbe_knowledgebase","type-kbe_knowledgebase","status-publish","has-post-thumbnail","hentry","kbe_taxonomy-academic-cluster-articles","kbe_taxonomy-user-guides"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.8.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Externally visible ssh server - arc-ssh - Academic Computing Team<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Externally visible ssh server - arc-ssh - Academic Computing Team\" \/>\n<meta property=\"og:description\" content=\"arc-ssh.reading.ac.uk is an externally visible ssh server. It exists to allow access to the UoR network and Linux-related resources from off-campus. Typical applications include accessing the Reading Academic Research Cluster (RACC), copying data using tools like sftp, scp or rsync, and secure access to other campus services via tunneled SOCKS proxy or port mapping.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/\" \/>\n<meta property=\"og:site_name\" content=\"Academic Computing Team\" \/>\n<meta property=\"article:modified_time\" content=\"2021-05-05T17:39:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/Unorganized\/ssh.png\" \/>\n\t<meta property=\"og:image:width\" content=\"256\" \/>\n\t<meta property=\"og:image:height\" content=\"256\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/\",\"url\":\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/\",\"name\":\"Externally visible ssh server - arc-ssh - Academic Computing Team\",\"isPartOf\":{\"@id\":\"https:\/\/research.reading.ac.uk\/act\/#website\"},\"datePublished\":\"2020-11-18T20:08:58+00:00\",\"dateModified\":\"2021-05-05T17:39:07+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/research.reading.ac.uk\/act\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Knowledgebase\",\"item\":\"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Externally visible ssh server &#8211; arc-ssh\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/research.reading.ac.uk\/act\/#website\",\"url\":\"https:\/\/research.reading.ac.uk\/act\/\",\"name\":\"Academic Computing Team\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/research.reading.ac.uk\/act\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/research.reading.ac.uk\/act\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/research.reading.ac.uk\/act\/#organization\",\"name\":\"University of Reading\",\"url\":\"https:\/\/research.reading.ac.uk\/act\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/research.reading.ac.uk\/act\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/2017\/08\/cropped-University_of_Reading_shield-1.png\",\"contentUrl\":\"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/2017\/08\/cropped-University_of_Reading_shield-1.png\",\"width\":512,\"height\":512,\"caption\":\"University of Reading\"},\"image\":{\"@id\":\"https:\/\/research.reading.ac.uk\/act\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Externally visible ssh server - arc-ssh - Academic Computing Team","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/","og_locale":"en_GB","og_type":"article","og_title":"Externally visible ssh server - arc-ssh - Academic Computing Team","og_description":"arc-ssh.reading.ac.uk is an externally visible ssh server. It exists to allow access to the UoR network and Linux-related resources from off-campus. Typical applications include accessing the Reading Academic Research Cluster (RACC), copying data using tools like sftp, scp or rsync, and secure access to other campus services via tunneled SOCKS proxy or port mapping.","og_url":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/","og_site_name":"Academic Computing Team","article_modified_time":"2021-05-05T17:39:07+00:00","og_image":[{"width":256,"height":256,"url":"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/Unorganized\/ssh.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_misc":{"Estimated reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/","url":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/","name":"Externally visible ssh server - arc-ssh - Academic Computing Team","isPartOf":{"@id":"https:\/\/research.reading.ac.uk\/act\/#website"},"datePublished":"2020-11-18T20:08:58+00:00","dateModified":"2021-05-05T17:39:07+00:00","breadcrumb":{"@id":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/arc-ssh\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/research.reading.ac.uk\/act\/"},{"@type":"ListItem","position":2,"name":"Knowledgebase","item":"https:\/\/research.reading.ac.uk\/act\/knowledgebase\/"},{"@type":"ListItem","position":3,"name":"Externally visible ssh server &#8211; arc-ssh"}]},{"@type":"WebSite","@id":"https:\/\/research.reading.ac.uk\/act\/#website","url":"https:\/\/research.reading.ac.uk\/act\/","name":"Academic Computing Team","description":"","publisher":{"@id":"https:\/\/research.reading.ac.uk\/act\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/research.reading.ac.uk\/act\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/research.reading.ac.uk\/act\/#organization","name":"University of Reading","url":"https:\/\/research.reading.ac.uk\/act\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/research.reading.ac.uk\/act\/#\/schema\/logo\/image\/","url":"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/2017\/08\/cropped-University_of_Reading_shield-1.png","contentUrl":"https:\/\/research.reading.ac.uk\/act\/wp-content\/uploads\/sites\/2\/2017\/08\/cropped-University_of_Reading_shield-1.png","width":512,"height":512,"caption":"University of Reading"},"image":{"@id":"https:\/\/research.reading.ac.uk\/act\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/kbe_knowledgebase\/6063","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/kbe_knowledgebase"}],"about":[{"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/types\/kbe_knowledgebase"}],"author":[{"embeddable":true,"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/users\/364"}],"version-history":[{"count":6,"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/kbe_knowledgebase\/6063\/revisions"}],"predecessor-version":[{"id":6577,"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/kbe_knowledgebase\/6063\/revisions\/6577"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/media\/5701"}],"wp:attachment":[{"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/media?parent=6063"}],"wp:term":[{"taxonomy":"kbe_taxonomy","embeddable":true,"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/kbe_taxonomy?post=6063"},{"taxonomy":"kbe_tags","embeddable":true,"href":"https:\/\/research.reading.ac.uk\/act\/wp-json\/wp\/v2\/kbe_tags?post=6063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}