<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/">
  <channel>
    <title>Passwords</title>
    <link>https://www.linuxjournal.com/</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Password Manager Roundup</title>
  <link>https://www.linuxjournal.com/content/password-manager-roundup</link>
  <description>  &lt;div data-history-node-id="1340417" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;If you can remember all of your passwords, they're not good passwords.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I used to teach people how to create "good" passwords. Those passwords
needed to be lengthy, hard to guess and easy to remember. There were lots
of tricks to make your passwords better, and for years, that was enough.&lt;/p&gt;

&lt;p&gt;
That's not enough anymore.
&lt;/p&gt;

&lt;p&gt;
It seems that another data breach happens almost daily, exposing sensitive
information for millions of users, which means you need to have separate, secure
passwords for each site and service you use. If you use the same password
for &lt;em&gt;any&lt;/em&gt; two sites, you're making yourself vulnerable if any single
database gets compromised.
&lt;/p&gt;

&lt;p&gt;
There's a much bigger conversation to be had regarding the best way to
protect data. Is the "password" outdated? Should we have something better
by now? Granted, there is two-factor authentication, which is a great way
to help increase the security on accounts. But although passwords remain
the main method for protecting accounts and data, there needs to be a
better way to handle them—that's where password managers come into play.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
The Best Password Manager&lt;/span&gt;

&lt;p&gt;
No, I'm not burying the lede by skipping all the reviews. As Doc Searls,
Katherine Druckman and myself discussed in &lt;a href="https://www.linuxjournal.com/podcast/episode-8-nostalgia-security-and-shawn"&gt;Episode 8 of the &lt;em&gt;Linux
Journal&lt;/em&gt;
Podcast&lt;/a&gt;, the best password manager is the one you &lt;em&gt;use&lt;/em&gt;. It may seem like a
cheesy thing to say, but it's a powerful truth. If it's more complicated
to use a password manager than it is to re-use the same set of passwords
on multiple sites, many people will just choose the easy way.
&lt;/p&gt;

&lt;p&gt;
Sure, some people are geeky enough to use a password manager
at any cost. They understand the value of privacy, understand security,
and they take their data very seriously. But for the vast majority of people,
the path of least resistance is the way to go. Heck, I'm guilty of that
myself in many cases. I have a Keurig coffee machine, not because the coffee
is better, but because it's more convenient. If you've ever eaten a
Hot Pocket instead of cooking a healthy meal, you can understand the
mindset that causes people to make poor password choices. If the goal is
having smart passwords, it needs to be easier to use smart passwords than
to type "password123" everywhere.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/password-manager-roundup" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 03 May 2019 11:00:00 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1340417 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>The Secret Password Is...</title>
  <link>https://www.linuxjournal.com/content/secret-password</link>
  <description>  &lt;div data-history-node-id="1084499" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/small-200px-left-align-wrap/u1002061/passwords-image.jpg" alt="" title="" class="imagecache-small-200px-left-align-wrap" /&gt;&lt;p&gt;
If your password is as easy as 123, we need to talk.
&lt;/p&gt;
&lt;p&gt;
The first password I ever remember using when I started in system
administration was ".redruM" (no quotes). It was by far the craftiest,
most-impossible-to-guess password ever conceived by a sentient
being. Sadly, a mere 17 years later (wow, it's been a long time!) that
password probably could be brute-force compromised in ten minutes—with
a cell phone.
&lt;/p&gt;

&lt;p&gt;
Since retinal scans still mainly are used in the movies to set the
scene for gruesome eyeball-stealing, for the foreseeable future (pun
intended), we're stuck with passwords. In this article, I want to take some
time to discuss best practices and give some thoughts on cool software
designed to help you keep your private affairs private. Before getting into
the how-to section, let me openly discuss the how-&lt;em&gt;not&lt;/em&gt;-to.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
The Things You Shall Not Do&lt;/span&gt;

&lt;p&gt;
&lt;em&gt;It's a bad idea to write your password on a sticky note
and affix it to your monitor.&lt;/em&gt;
&lt;/p&gt;

&lt;p&gt;
Yes, it sounds like a joke, but this happens every day—in almost every
business. In fact, sometimes tech folks are guilty of this cardinal sin
because they've changed passwords for users and need to let them know
their new passwords. Seeing your password written or typed out should
cause you physical pain and distress. Displaying it on your monitor is
just wrong.
&lt;/p&gt;

&lt;p&gt;
&lt;em&gt;It's a bad idea to use any of the following as your
password, or at least as your entire password:&lt;/em&gt;
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;
&lt;p&gt;
Your pet's name, current or past.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Your child's name or nickname.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Your car's name, model or a car you want.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Birth dates of any people you know.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Name of your college/high-school mascot.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Anything related to your hobbies.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Your address in any form.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Your telephone number, past or present.
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Your mother's maiden name (this is less secure than .redruM).
&lt;/p&gt;&lt;/li&gt;

&lt;li&gt;
&lt;p&gt;
Any of the following: password, 123456, abc123, letmein, love, iloveyou, sex, god, trustno1,
master, asdfjkl;, qwerty, password123, secret, jesus or ninja.
&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
If I've just described your password or, heaven forbid, actually listed
it in the last bullet point (some of the most common passwords), you
need to keep reading. Don't change your password yet though, as I'm going
to discuss best practices next, but even if you don't read another word,
you can't leave your password like it is—really.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/secret-password" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 19 Apr 2013 15:00:00 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1084499 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
