<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenSSH on Michael’s Domain</title><link>https://jeltsch.org/en/tags/openssh/</link><description>Recent content in OpenSSH on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/openssh/index.xml" rel="self" type="application/rss+xml"/><item><title>Remote desktop sessions to your Helsinki University work computer</title><link>https://jeltsch.org/en/remote_desktop_sessions_to_your_helsinki_university_work_computer/</link><pubDate>Mon, 15 Jan 2018 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/remote_desktop_sessions_to_your_helsinki_university_work_computer/</guid><description>&lt;p&gt;If you have a work laptop, you can take it home to do work. But what if you have a desktop computer and need to access it from home? The technology to make this possible exists for more than 20 years, but if you think that University IT has made this easy for you, you would be wrong. In fact, I don&amp;rsquo;t know anybody who knows how to do this (let alone how to make the process easy). Even with the setup explained below, some things do not work well (e.g. I never could figure out how to get the file sharing to work with a Mac-to-Mac connection and thus I still use 
 &lt;a href="http://rsug.itd.umich.edu/software/fugu/" target="_blank" rel="noopener noreferrer nofollow"&gt;Fugu&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 with a separate tunnelled sftp connection to transfer files). You have several options:&lt;/p&gt;</description></item><item><title>How to start openvpn or ssh server under Ubuntu 16.04 and 18.04</title><link>https://jeltsch.org/en/how_to_start_openvpn_or_ssh_server_under_ubuntu_16_04_and_18_04/</link><pubDate>Sat, 03 Sep 2016 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/how_to_start_openvpn_or_ssh_server_under_ubuntu_16_04_and_18_04/</guid><description>&lt;p&gt;&lt;strong&gt;OpenVPN&lt;/strong&gt;&lt;code&gt;sudo systemctl start openvpn@client&lt;/code&gt;The &amp;ldquo;client&amp;rdquo; is derived from the configuration file name (/etc/openvpn/client.conf). If your configuration file is server.conf, the command needs to be&lt;code&gt;sudo systemctl start openvpn@server&lt;/code&gt;When you want the service to start up automatically during system boot, you issue:&lt;code&gt;sudo systemctl enable openvpn@server&lt;/code&gt;&lt;strong&gt;Templated versus non-templated services&lt;/strong&gt;OpenVPN is a so-called &amp;ldquo;templated&amp;rdquo; service (it needs a configuration file when being invoked). In contrast to this, the ssh server is a non-templated service. Hence the command is simpler:&lt;code&gt;sudo systemctl start sshd&lt;/code&gt;&lt;/p&gt;</description></item></channel></rss>