<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>passwords on gkourgkoutas.net</title>
    <link>https://gkourgkoutas.net/en/tags/passwords/</link>
    <description>Recent content in passwords on gkourgkoutas.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Fri, 06 Nov 2020 21:33:59 +0100</lastBuildDate><atom:link href="https://gkourgkoutas.net/en/tags/passwords/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Passwords</title>
      <link>https://gkourgkoutas.net/en/posts/passwords/</link>
      <pubDate>Fri, 06 Nov 2020 21:33:59 +0100</pubDate>
      
      <guid>https://gkourgkoutas.net/en/posts/passwords/</guid>
      <description>It&amp;rsquo;s rather bad than complex A lot of users1 always choose their passwords based on the same criteria:
  They use the same password for every service
password reuse
  They use a combination of username + year of birth
user95
  The classic par excellence: season + year
Winter2020
  With common password lists, these kind of passwords can be found out in seconds. Even if they&amp;rsquo;re hashed, cracking them with tools like Hashcat2 in combination with rule based lists3 and potent hardware is not a big effort.</description>
    </item>
    
  </channel>
</rss>
