<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
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/"
> <channel><title>Comments on: How to choose a root password that you&#8217;ll remember</title> <atom:link href="http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember/feed/" rel="self" type="application/rss+xml" /><link>http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember/</link> <description>Continuous Integration, Delivery and Devops Consulting</description> <lastBuildDate>Thu, 02 Feb 2012 22:31:14 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Steve Robb</title><link>http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember/comment-page-1/#comment-1395</link> <dc:creator>Steve Robb</dc:creator> <pubDate>Wed, 29 Jun 2011 17:56:07 +0000</pubDate> <guid
isPermaLink="false">http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember#comment-1395</guid> <description>My team has been using Secret Server for a while now.
It is designed for sysadmin teams - basically a web-based password vault with permissions, etc but can also test and actually change passwords for you.
http://www.thycotic.com
We have it randomizing our root passwords on a schedule.  We also dabbled with the checkout where it changes the root password 30 minutes after you use it.</description> <content:encoded><![CDATA[<p>My team has been using Secret Server for a while now.</p><p>It is designed for sysadmin teams &#8211; basically a web-based password vault with permissions, etc but can also test and actually change passwords for you.<br
/> <a
href="http://www.thycotic.com" rel="nofollow">http://www.thycotic.com</a></p><p>We have it randomizing our root passwords on a schedule.  We also dabbled with the checkout where it changes the root password 30 minutes after you use it.</p> ]]></content:encoded> </item> <item><title>By: simpsonjulian</title><link>http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember/comment-page-1/#comment-307</link> <dc:creator>simpsonjulian</dc:creator> <pubDate>Fri, 03 Apr 2009 10:23:54 +0000</pubDate> <guid
isPermaLink="false">http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember#comment-307</guid> <description>@ken - I did penance and wrote a new post.
@jtf - fair point - although it does remind me of the passwords that compuserve would hand out with their free floppy disks in the 90s.  Maybe I was the only one to actually use those ...</description> <content:encoded><![CDATA[<p>@ken &#8211; I did penance and wrote a new post.<br
/> @jtf &#8211; fair point &#8211; although it does remind me of the passwords that compuserve would hand out with their free floppy disks in the 90s.  Maybe I was the only one to actually use those &#8230;</p> ]]></content:encoded> </item> <item><title>By: Don&#8217;t be disco, use sudo &#124; The Build Doctor</title><link>http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember/comment-page-1/#comment-305</link> <dc:creator>Don&#8217;t be disco, use sudo &#124; The Build Doctor</dc:creator> <pubDate>Thu, 02 Apr 2009 22:25:31 +0000</pubDate> <guid
isPermaLink="false">http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember#comment-305</guid> <description>[...] comment from Ken Mayer on my post about root passwords: No one should ever use “root” for anything except single-user mode emergencies and initial [...]</description> <content:encoded><![CDATA[<p>[...] comment from Ken Mayer on my post about root passwords: No one should ever use “root” for anything except single-user mode emergencies and initial [...]</p> ]]></content:encoded> </item> <item><title>By: Ken Mayer</title><link>http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember/comment-page-1/#comment-304</link> <dc:creator>Ken Mayer</dc:creator> <pubDate>Thu, 02 Apr 2009 11:29:29 +0000</pubDate> <guid
isPermaLink="false">http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember#comment-304</guid> <description>I respectfully disagree with the premise.
No one should ever use &quot;root&quot; for &lt;em&gt;anything&lt;/em&gt; except single-user mode emergencies and initial configuration. Make it a long string of random characters and store it in a safe or encrypted on a secure hard drive. Make it unique for every box. Then forget about it.
Use sudo instead. Leaving sudo&#039;s arcane configuration syntax aside for the moment, using sudo means every action is logged with a real person&#039;s name and a time stamp. Another good reason: you don&#039;t have to change the root password if someone quits or is fired.
Use a password vault (like 1Password for the Mac -- there are many others). Make every single password unique, long and as random as possible. Then make your &lt;em&gt;master&lt;/em&gt; password &lt;strong&gt;really&lt;/strong&gt; hard to guess, but easy to remember (the first letter of each word from a long sentence, FIPS standards, two random words glued together by a figure or gliph, the suggestions here). And just in case you&#039;re run down by the Budweiser Beer Wagon one day, write it down and put it in a locked safe -- to be opened when you are beyond caring.</description> <content:encoded><![CDATA[<p>I respectfully disagree with the premise.</p><p>No one should ever use &#8220;root&#8221; for <em>anything</em> except single-user mode emergencies and initial configuration. Make it a long string of random characters and store it in a safe or encrypted on a secure hard drive. Make it unique for every box. Then forget about it.</p><p>Use sudo instead. Leaving sudo&#8217;s arcane configuration syntax aside for the moment, using sudo means every action is logged with a real person&#8217;s name and a time stamp. Another good reason: you don&#8217;t have to change the root password if someone quits or is fired.</p><p>Use a password vault (like 1Password for the Mac &#8212; there are many others). Make every single password unique, long and as random as possible. Then make your <em>master</em> password <strong>really</strong> hard to guess, but easy to remember (the first letter of each word from a long sentence, FIPS standards, two random words glued together by a figure or gliph, the suggestions here). And just in case you&#8217;re run down by the Budweiser Beer Wagon one day, write it down and put it in a locked safe &#8212; to be opened when you are beyond caring.</p> ]]></content:encoded> </item> <item><title>By: Jeffrey Fredrick</title><link>http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember/comment-page-1/#comment-306</link> <dc:creator>Jeffrey Fredrick</dc:creator> <pubDate>Thu, 02 Apr 2009 07:26:53 +0000</pubDate> <guid
isPermaLink="false">http://www.build-doctor.com/2009/03/31/how-to-choose-a-root-password-that-youll-remember#comment-306</guid> <description>That seems a bit retro, like you&#039;ve got a limited number of characters for your password. Why not &quot;&lt;code&gt;PeetsCoffeeTea1!&lt;/code&gt;&quot;?</description> <content:encoded><![CDATA[<p>That seems a bit retro, like you&#8217;ve got a limited number of characters for your password. Why not &#8220;<code>PeetsCoffeeTea1!</code>&#8220;?</p> ]]></content:encoded> </item> </channel> </rss>
