On Thu, Jan 31, 2013 at 9:16 AM, David Lum <[email protected]> wrote: > For a twitter account: Twitter1 vodka eagles! > Then for a Facebook account:Facebook2 vodka eagles! > > Then follow that same pattern for the various accounts. While it seems like > bad practice to include the service name as part of the password I thought > I’d ask your guys’ opinion. It’s at least better than using the same > password for everything…or is it?
Problem there, once the password is cracked, it's cracked for all the other services, too. I suppose it might stop some unsophisticated, strictly automated attacks, i.e., someone's got an entire database and is just going after the low-hanging fruit. But ultimately, it's approaching the problem the wrong way, so you're just going further down the wrong road. Better to have a working solution. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
