<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Security on Wapnet Blog</title><link>https://blog.wapnet.nl/category/security/</link><description>Recent content in Security on Wapnet Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 03 Nov 2026 12:00:00 +0100</lastBuildDate><atom:link href="https://blog.wapnet.nl/category/security/feed.xml" rel="self" type="application/rss+xml"/><item><title>Safely Updating Hermes When Hermes Runs in Docker</title><link>https://blog.wapnet.nl/2026/11/safely-updating-hermes-when-hermes-runs-in-docker/</link><pubDate>Tue, 03 Nov 2026 12:00:00 +0100</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/2026/11/safely-updating-hermes-when-hermes-runs-in-docker/</guid><description>&lt;p&gt;&lt;strong&gt;The Problem&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I run &lt;a href="https://hermes-agent.nousresearch.com/"&gt;Hermes&lt;/a&gt; as a Docker container. Asking it to pull its own new image is easy. Letting that same container recreate itself is where things get interesting.&lt;/p&gt;
&lt;p&gt;A normal update looks harmless:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;docker compose pull hermes
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;docker compose up -d --force-recreate hermes
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;But when Hermes runs those commands from inside itself, &lt;code&gt;docker compose up&lt;/code&gt; removes the container that is currently executing the update. The SSH session, shell or agent call can disappear after the old container is removed but before the replacement is started. The result is a Hermes container stuck in &lt;code&gt;Created&lt;/code&gt;, and nobody left to finish the command.&lt;/p&gt;</description></item><item><title>Turning an Android Phone into a Remote LAN Probe with Tailscale and Hermes</title><link>https://blog.wapnet.nl/2026/11/turning-an-android-phone-into-a-remote-lan-probe-with-tailscale-and-hermes/</link><pubDate>Sun, 01 Nov 2026 12:00:00 -0400</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/2026/11/turning-an-android-phone-into-a-remote-lan-probe-with-tailscale-and-hermes/</guid><description>&lt;p&gt;&lt;strong&gt;The Goal&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I wanted to disable audio recording on one security camera. The RXCamView app could mute live playback, but that does not stop the recorder from saving audio. For that I needed the recorder&amp;rsquo;s web interface.&lt;/p&gt;
&lt;p&gt;Small problem: I did not know its IP address. I had only my Android phone on the same Wi-Fi network, while &lt;a href="https://hermes-agent.nousresearch.com/"&gt;Hermes&lt;/a&gt; was running on a server somewhere else.&lt;/p&gt;
&lt;p&gt;That phone was already connected to my Tailscale network. Could Hermes use it as a remote &lt;code&gt;nmap&lt;/code&gt; probe?&lt;/p&gt;</description></item><item><title>Self-hosted Vaultwarden with Cloudflare Tunnel and mTLS</title><link>https://blog.wapnet.nl/2026/03/self-hosted-vaultwarden-with-cloudflare-tunnel-and-mtls/</link><pubDate>Sun, 22 Mar 2026 00:25:33 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=2272</guid><description>&lt;p&gt;I was using tailscale + vaultwarden before but I don&amp;rsquo;t want to use a VPN connection to access my passwords. But I do want a client certificate for extra security.&lt;/p&gt;
&lt;p&gt;So I write this to guide to exposing Vaultwarden securely via Cloudflare Tunnel, protected by mutual TLS (mTLS) client certificates. No open ports required.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Please note: it looks like iOS bitwarden app don&amp;rsquo;t have the option to import a mtls certificate&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Install Pihole on Synology with docker</title><link>https://blog.wapnet.nl/2020/05/install-pihole-on-synology-with-docker/</link><pubDate>Tue, 12 May 2020 21:49:06 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=1847</guid><description>&lt;p&gt;Unfortunately, there isn&amp;rsquo;t a pihole addon in the Synology package center. But you can build your pihole in a docker container instead :)&lt;/p&gt;
&lt;p&gt;The reason you must use docker-compose instead of the Synology docker package itself is that you want to bridge net NIC of your Synology and place the pihole direct in your network. You cannot do this with the GUI.&lt;/p&gt;
&lt;h2 id="the-steps"&gt;The steps:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Install docker with the package center&lt;/li&gt;
&lt;li&gt;Activate SSH&lt;/li&gt;
&lt;li&gt;Download de image pihole/pihole:latest&lt;/li&gt;
&lt;li&gt;Login with ssh&lt;/li&gt;
&lt;li&gt;type vi docker-compose.yaml&lt;/li&gt;
&lt;li&gt;Paste the content from the docker-compose.yaml example into the vi&lt;/li&gt;
&lt;li&gt;Change the IP adressen to your own network&lt;/li&gt;
&lt;li&gt;Type :wr to save the file&lt;/li&gt;
&lt;li&gt;Type :q to quit vi&lt;/li&gt;
&lt;li&gt;Type &amp;ldquo;sudo docker-compose up&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Have fun!&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="docker-composeyaml-example"&gt;Docker-compose.yaml Example&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;# Note: 192.168.123.xxx is an example network, you must update all these to match your own.
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;version: &amp;#39;2&amp;#39;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;services:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; pihole:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; container_name: pihole
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; image: pihole/pihole:latest
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; hostname: pihole
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; domainname: localhost # &amp;lt;-- Update
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; mac_address: d0:ca:ab:cd:ef:01
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; cap_add:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - NET_ADMIN
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; networks:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; pihole_network:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ipv4_address: 192.168.123.199 # &amp;lt;-- Update
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; dns:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - 127.0.0.1
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - 1.1.1.1
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ports:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - 443/tcp
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - 53/tcp
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - 53/udp
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - 67/udp
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - 80/tcp
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; environment:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ServerIP: 192.168.123.199 # &amp;lt;-- Update (match ipv4_address)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; VIRTUAL_HOST: pihole.localhost # &amp;lt;-- Update (match hostname + domainname)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; WEBPASSWORD: &amp;#34;justarondompassword&amp;#34; # &amp;lt;-- Add password (if required)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; restart: unless-stopped
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;networks:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; pihole_network:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; driver: macvlan
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; driver_opts:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; parent: ovs_eth0
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ipam:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; config:
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; - subnet: 192.168.123.0/24 # &amp;lt;-- Update
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; gateway: 192.168.123.1 # &amp;lt;-- Update
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ip_range: 192.168.123.192/28 # &amp;lt;-- Update
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;When you want to update the docker container, all you have to do is:&lt;/p&gt;</description></item><item><title>Create a strong self-signed certificate for multiple years</title><link>https://blog.wapnet.nl/2016/11/create-a-strong-self-signed-certificate-for-multiple-years/</link><pubDate>Sat, 12 Nov 2016 16:52:15 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=1744</guid><description>&lt;p&gt;If you follow these steps you can create a self signed certificate with the following specifications:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Wildcard certificate&lt;/li&gt;
&lt;li&gt;SHA256 hash&lt;/li&gt;
&lt;li&gt;10 years&lt;/li&gt;
&lt;li&gt;2048 bits public key&lt;/li&gt;
&lt;li&gt;Client and server verification&lt;/li&gt;
&lt;li&gt;Sha1 fingerprint&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Be aware that self-signed certificates can manipulate by a man-in-the-middle. You should not use this in critical production environments.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Please use windows 10 powershell in admin mode. Otherwise you will get errors&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;New-SelfSignedCertificate -certstorelocation cert:\localmachine\my -dnsname *.domain.local -NotBefore $([datetime]::now.AddDays(-15)) -NotAfter $([datetime]::now.AddDays(3560))
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Now export the certificates. Before you copy/paste change the thumbprint with the thumbprint you get from the above command.&lt;/p&gt;</description></item><item><title>Convert PFX to PEM and upload the certificate to Plesk</title><link>https://blog.wapnet.nl/2015/12/convert-pfx-to-pem-and-upload-the-certificate-to-plesk/</link><pubDate>Mon, 21 Dec 2015 16:16:00 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=1677</guid><description>&lt;p&gt;Export the Private Key:
`&lt;/p&gt;
&lt;h1 id="openssl-pkcs12--in-filenamepfx--nocerts--out-keypem"&gt;openssl pkcs12 -in filename.pfx -nocerts -out key.pem&lt;/h1&gt;
&lt;p&gt;&lt;code&gt;Remove the password from the SSL certificate (unencrypted is needed for plesk):&lt;/code&gt;&lt;/p&gt;
&lt;h1 id="openssl-rsa--in-keypem--out-serverkey"&gt;openssl rsa -in key.pem -out server.key&lt;/h1&gt;
&lt;p&gt;&lt;code&gt;Export the certificate:&lt;/code&gt;&lt;/p&gt;
&lt;h1 id="openssl-pkcs12--in-filenamepfx--clcerts--nokeys--out-certpem"&gt;openssl pkcs12 -in filename.pfx -clcerts -nokeys -out cert.pem&lt;/h1&gt;
&lt;p&gt;`&lt;/p&gt;
&lt;p&gt;Now upload the certificate:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.wapnet.nl/wp-content/uploads/2015/12/SSL-thawte.png"&gt;&lt;img alt="ssl-thawte" loading="lazy" src="https://blog.wapnet.nl/wp-content/uploads/2015/12/SSL-thawte.png"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;And bind the certificate in your hosting settings:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.wapnet.nl/wp-content/uploads/2015/12/SSL-PII.png"&gt;&lt;img alt="SSL-PII" loading="lazy" src="https://blog.wapnet.nl/wp-content/uploads/2015/12/SSL-PII.png"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Brute force example MD5 password using hashcat</title><link>https://blog.wapnet.nl/2015/02/brute-force-example-md5-password-using-hashcat/</link><pubDate>Sun, 08 Feb 2015 15:45:16 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=1589</guid><description>&lt;p&gt;&lt;code&gt;hashcat -n 2 -m 0 -a 3 --pw-min 9 hashfile.txt ?l?l?l?l?l?l?l?l?l?l&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;-n = 2 threads
-m 0 = md5
&amp;ndash;pw-min 9 = minimal 9 characters
hashfile.txt = is txt file where the hash is located
&lt;code&gt;?l?l?l?l?l?l?l?l?l?l&lt;/code&gt; = lowercase password&lt;/p&gt;
&lt;p&gt;Have fun!&lt;/p&gt;</description></item><item><title>Social hacking with FOCA</title><link>https://blog.wapnet.nl/2015/01/social-hacking-with-foca/</link><pubDate>Sun, 11 Jan 2015 20:08:55 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=1577</guid><description>&lt;p&gt;Social hacking starts with:  FOCA ( &lt;strong&gt;Fingerprinting Organizations with Collected Archives&lt;/strong&gt;)&lt;/p&gt;
&lt;p&gt;Happy hacking :)&lt;/p&gt;
&lt;p&gt;URL: &lt;a href="https://www.elevenpaths.com/labstools/foca/index.html"&gt;https://www.elevenpaths.com/labstools/foca/index.html&lt;/a&gt; &lt;a href="https://blog.wapnet.nl/wp-content/uploads/2015/01/FOCA.png"&gt;&lt;img alt="FOCA" loading="lazy" src="https://blog.wapnet.nl/wp-content/uploads/2015/01/FOCA.png"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Zenoss reverse proxy with Pound (CentOS)</title><link>https://blog.wapnet.nl/2014/02/zenoss-reverse-proxy-with-pound-centos/</link><pubDate>Thu, 27 Feb 2014 14:38:16 +0000</pubDate><guid isPermaLink="false">https://blog.wapnet.nl/?p=1503</guid><description>&lt;p&gt;Zenoss don&amp;rsquo;t support SSL certificates out-of-the-box. If you want to use an SSL connection to your zenoss monitor server the only thing you can do is use an reverse proxy. You can use this howto to install and configure a pound reverse proxy.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Install pound with the EPEL&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Install the EPEL (more info about &lt;a href="https://fedoraproject.org/wiki/EPEL"&gt;EPEL&lt;/a&gt;) repository with these commands:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-gdscript3" data-lang="gdscript3"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;su &lt;span style="color:#f92672"&gt;-&lt;/span&gt;c &lt;span style="color:#e6db74"&gt;&amp;#39;rpm -Uvh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;yum update
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Install pound&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;yum install pound
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;strong&gt;Install pound without the EPEL&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>