Site updated at 2017-12-29 08:24:20 UTC

This commit is contained in:
Travis CI 2017-12-29 08:24:20 +00:00
parent 634126eaf6
commit ef08aef875
236 changed files with 1815 additions and 1510 deletions

View file

@ -67,6 +67,33 @@
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/11/02/secure-shell-tunnel/">Home Assistant and SSH</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-11-02T08:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> November 02, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> three minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/11/02/secure-shell-tunnel/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Most system engineers are very familiar with <a href="https://en.wikipedia.org/wiki/Secure_Shell">SSH (Secure shell)</a>. This tool which contains a server part and a client part is used to access a remote system in a secure way. It can also help you if your are running Home Assistant but dont want to expose it to the public. On a Linux system SSH is often available by default. If you are using a Windows installation additional steps are required which are not covered here.</p>
<p>In this blog post we are going to use the tunneling option of SSH to create a secure connection and forward the Home Assistant frontend to a local system.</p>
<a class="btn pull-right" href="/blog/2017/11/02/secure-shell-tunnel/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -426,55 +453,6 @@
<p>Are you not a programmer but still want to contribute to Home Assistant? Check out our <a href="https://github.com/home-assistant/home-assistant.github.io/labels/Hacktoberfest">list of entry-level issues for the Home Assistant website</a>.</p>
<p>Our participation for <a href="https://home-assistant.io/blog/2016/11/05/hacktoberfest-influxdb-weather/#hacktoberfest">Hacktoberfest 2016</a> was a huge success. Join us to repeat it this year.</p>
<p><a href="https://hacktoberfest.digitalocean.com/"><img src="/images/blog/2016-10-hacktoberfest/hacktoberfest.png" alt="Hacktober fest logo" /></a></p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/">Effortless encryption with Let's Encrypt and DuckDNS</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-09-27T00:05:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> September 27, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> two minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>When Lets Encrypt launched we were estatic: finally an easy and free way for our users to securely access their homes remotely. Lets Encrypt signifianctly lowered the bar to get and renew SSL certificates. However, this process could still be quite an obstacle for our users. It required opening ports on the router and remembering to renew the certificate every so often.</p>
<p>Thanks to a <a href="https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt">blog post</a> by Andreas Gohr I realized that DuckDNS supports setting TXT records, making it compatible with the DNS-01 challenge of Lets Encrypt. The DNS-01 challenge is using the DNS record of the domain instead of interacting with the server. This means that its not needed for the user to open any ports!</p>
<p>I have worked together with <a href="https://github.com/pvizeli">Pascal Vizeli</a> on updating the DuckDNS add-on for Hass.io and today were proud to announce it now includes automatic generation and updating of Lets Encrypt certificates for your DuckDNS domain. The only thing that you have to add to your DuckDNS configuration is that you accept the Lets Encrypt <a href="https://letsencrypt.org/repository/">terms of service</a> and point Home Assistant at the generated certificates and youre good to go. No other work is required.</p>
<p>To get started today, start with making sure that you have <a href="/hassio/">Hass.io installed</a>. After that, go to the Hass.io panel in Home Assistant, open the add-on store, scroll down to DuckDNS and install it. In the DuckDNS settings change “accept_terms” to true and start it.</p>
<p>Next up is to configure Home Assistant with the config below and restart it. Youre now good to go! Make sure to use the right protocol when browsing to your instance: <code class="highlighter-rouge">https://&lt;your_domain&gt;.duckdns.org</code>. Happy secure controlling your house!</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry for the HTTP component</span>
<span class="s">http</span><span class="pi">:</span>
<span class="s">ssl_certificate</span><span class="pi">:</span> <span class="s">/ssl/fullchain.pem</span>
<span class="s">ssl_key</span><span class="pi">:</span> <span class="s">/ssl/privkey.pem</span>
</code></pre>
</div>
<p>If youre not using Hass.io, check out the <a href="https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt">blog post</a> by Andreas for instructions.</p>
<p>If you enjoy the free service provided by DuckDNS and Lets Encrypt, consider donating to their cause:</p>
<ul>
<li><a href="https://www.patreon.com/user?u=3209735">Become a Patreon of DuckDNS</a></li>
<li><a href="https://letsencrypt.org/donate/">Donate to Lets Encrypt</a></li>
</ul>
<p>More information:</p>
<ul>
<li><a href="/hassio/">Hass.io</a></li>
<li><a href="/hassio/installation/">Installing Hass.io</a></li>
<li><a href="/addons/duckdns/">DuckDNS add-on</a></li>
<li><a href="http://www.duckdns.org/">DuckDNS</a></li>
<li><a href="https://letsencrypt.org/">Lets Encrypt</a></li>
</ul>
</div>
</article>
<hr>