TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: Secure password explanation? From:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> To:yehoshua paul <yehoshua -dot- p -at- technicalwriting -dot- com> Date:Tue, 19 Jun 2012 12:17:58 -0400
You are probably correct.
So, for my own documents, I'm not going to bother importing that particular "security" practice from that particular example company.
As a very occasional user of company O's product, I have defaulted to the (much-despised) method described by another poster - get the admin to reset my password whenever I need to actually access the database.
As the writer for my own company's products, however, I remain on the lookout for security best-practices that I can convey to my readers, but only if those practices are helpful to the reader and not just a convenience for some DBA somewhere.
Cheers,
-k
From: ysp10182 -at- gmail -dot- com [mailto:ysp10182 -at- gmail -dot- com] On Behalf Of yehoshua paul
Sent: June-18-12 12:15 PM
To: McLauchlan, Kevin
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Secure password explanation?
Because it's easier to create a universal rule banning double characters than come up with a specific rule for each pattern that leads to a weak password. For example "aabbccdd" or "111444."
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
