<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>misc &#8211; Robert&#039;s private homepage</title>
	<atom:link href="http://rehner.org/archives/category/misc/feed" rel="self" type="application/rss+xml" />
	<link>http://rehner.org</link>
	<description></description>
	<lastBuildDate>Thu, 09 Mar 2017 10:23:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Automated Let&#8217;s Encrypt with Certbot for Apache Running on a Different Port</title>
		<link>http://rehner.org/archives/204</link>
		
		<dc:creator><![CDATA[Robert]]></dc:creator>
		<pubDate>Thu, 09 Mar 2017 10:23:30 +0000</pubDate>
				<category><![CDATA[misc]]></category>
		<guid isPermaLink="false">http://rehner.org/?p=204</guid>

					<description><![CDATA[If you want to use Let&#8217;s Encrypt certificates with your Apache server, but you have changed the port for HTTPS to something else than 443, things get a bit tricky. You can (obviously) go for the manual installation or use &#8230; <a href="http://rehner.org/archives/204">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<p>If you want to use Let&#8217;s Encrypt certificates with your Apache server, but you have changed the port for HTTPS to something else than 443, things get a bit tricky.</p>
<p>You can (obviously) go for the manual installation or use DNS auth if you can easily access your DNS server. But, if you have a very simple setup, like a server being behind a NAT and running on a different port, the standard way of using certbot no longer works.</p>
<p>I found the following setup to be working:</p>
<ul>
<li>Set up a port forward for port 443 in your NAT. Since your server does not use this port, this will not do anything, yet.</li>
<li>Install certbot according to their tutorial</li>
<li>Now you would normally do
<pre>$ ./path/to/certbot-auto --apache</pre>
<p>But this won&#8217;t work because you are using a different port.</li>
<li>Instead do a manual authentiation with
<pre>./certbot-auto certonly --standalone</pre>
</li>
<li>Follow the instructions to obtain the certificate.</li>
<li>Next, you can install the certificate yourself, or be lazy and use certbot&#8217;s installer for apache. Since you want it only to do the install (and not the authentication again) you have to call it like this:
<pre>./certbot-auto install --apache --cert-path /etc/letsencrypt/live/&lt;your-domain&gt;/fullchain.pem --key-path /etc/letsencrypt/live/&lt;your-domain&gt;/privkey.pem --chain-path /etc/letsencrypt/live/&lt;your-domain&gt;/fullchain.pem -d &lt;your-domain&gt;</pre>
</li>
<li>Adapt the paths accordingly to what the &#8211;standalone run of certbot told you.</li>
</ul>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Comfortable search the arpwatch database</title>
		<link>http://rehner.org/archives/196</link>
		
		<dc:creator><![CDATA[Robert]]></dc:creator>
		<pubDate>Tue, 25 Oct 2016 22:08:46 +0000</pubDate>
				<category><![CDATA[misc]]></category>
		<guid isPermaLink="false">http://rehner.org/?p=196</guid>

					<description><![CDATA[If you use arpwatch to track what is going on in your network you will eventually search for an IP or MAC address in the arp.dat file. Here is a simple bash script which gives a nicer output than just &#8230; <a href="http://rehner.org/archives/196">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<p>If you use arpwatch to track what is going on in your network you will eventually search for an IP or MAC address in the arp.dat file. Here is a simple bash script which gives a nicer output than just using grep and it also converts the unix timestamp to a more human friendly format:</p>
<pre class="brush: bash; title: ; notranslate">
#!/bin/bash

cat /var/lib/arpwatch/arp.dat | grep $1 |  awk  '{$3=strftime(&quot;%Y-%m-%d %H:%M:%S&quot;, $3);printf &quot;%-20s %-20s %s %s\n&quot;,$1,$2,$3,$4}'
</pre>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
