<?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>Docker on DLRS</title>
    <link>https://dlrs.me/tags/docker/</link>
    <description>Recent content in Docker on DLRS</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 24 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dlrs.me/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fingerprint simulator </title>
      <link>https://dlrs.me/posts/fingerprint-simulator/</link>
      <pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://dlrs.me/posts/fingerprint-simulator/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a common misconception about biometrics and cybersecurity, this misconception is that you can&amp;rsquo;t get infected or compromised just by visiting a site&lt;/p&gt;
&lt;p&gt;Spoiler alert: You can.&lt;/p&gt;
&lt;p&gt;I built this fingerprint simulator to demostrate to some extent what a malicious website or a rogue ad can gather from an user simply by having them load the page&amp;ndash;and what a threat actor can do with that information.&lt;/p&gt;
&lt;p&gt;For legal reasons and ethical reasons I had to go from real visitor data to generating a fake visitor every 10 seconds. All of this because this project showcases all the information gathered to all the public, displaying all this information from real users would be a privacy nightmare, moreso considering that I actually check for CVEs (Common Vulnerability and Exposures), and I check their IP against known data leaks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
