Idea from Security Now podcast - Use a hash
on
Too Many Passwords
·
· Score: 1
One of the Security Now podcasts had a good sugesstion to have a unique password algorithm (IMO a good suggestion). The algorithm is the same for each website, but the password itself is different for each website. For example, the inputs for the algorithm would be: the name of the website, and, some kind of hash unique to you. You insert the hash somewhere into the name of the website. Suchlike:
Then password: hot#somekindofnumericalsequence#mail
The point is, it's easy to remember a password formuala/algorith that applies to many, many places rather than trying to remember manay, many passwords. You don't even have to write them down.
That's a flawed scenario. The fact that any track exists in iTMS suggests it CAN be found elsewhere; unless if it's an iTunes exclusive track, which I haven't seen too many obscure 30 year old B-sides as an iTunes exclusive tracks. iTMS sells what is available.
Even with your clarification it is still a bad analogy. The nature of the distribution methods are so different that a comparison is a bit of a reach..
It would be like the BBC distributing copies of its performances physically stuck in most of CD players sold and almost imposible to get out.
Bad analogy.
Sure IE was given away for free but the average user had to take no action to get IE since it was the default browser for many a windows install. People are making an effort and choosing to download the BCC recordings.
An analogy to your analogy would be if somehow the BBC recordings (IE) were able to pre-empt any other performance (browser) when I want to listen to classical music (get on the net).
Slashdot Mirror
...that gives worms to ex-girlfriends!"
http://www.democracynow.org/ itunes link http://phobos.apple.com/WebObjects/MZStore.woa/wa/ viewPodcast?id=73802554
One of the Security Now podcasts had a good sugesstion to have a unique password algorithm (IMO a good suggestion). The algorithm is the same for each website, but the password itself is different for each website. For example, the inputs for the algorithm would be: the name of the website, and, some kind of hash unique to you. You insert the hash somewhere into the name of the website. Suchlike:
website: slashdot
hash: #somekindofnumericalsequenc#
Then
password: slah#somekindofnumericalsequence#dot
or
website: hotmail
hash: #somekindofnumericalsequenc#
Then
password: hot#somekindofnumericalsequence#mail
The point is, it's easy to remember a password formuala/algorith that applies to many, many places rather than trying to remember manay, many passwords. You don't even have to write them down.
That's a flawed scenario. The fact that any track exists in iTMS suggests it CAN be found elsewhere; unless if it's an iTunes exclusive track, which I haven't seen too many obscure 30 year old B-sides as an iTunes exclusive tracks. iTMS sells what is available.
How is a track defined as "hard to find" if it's in iTMS? Hard to find means you can't find it in iTMS.
Even with your clarification it is still a bad analogy. The nature of the distribution methods are so different that a comparison is a bit of a reach.. It would be like the BBC distributing copies of its performances physically stuck in most of CD players sold and almost imposible to get out.
That's not too far off, you can get a 26" samsung with built in HD tuner for $650. You can get just HD monitors now for $500.
Bad analogy. Sure IE was given away for free but the average user had to take no action to get IE since it was the default browser for many a windows install. People are making an effort and choosing to download the BCC recordings. An analogy to your analogy would be if somehow the BBC recordings (IE) were able to pre-empt any other performance (browser) when I want to listen to classical music (get on the net).
Back to the pile!!!
"Back to the pile!!!"