Trouble is once they have access to that garbage email account, they can sign you up for services using it along with other easily had information like your birthday, place of residence, etc.. And a lot of times they don't even have to get all of it right, comanies don't double check it, all they're interested in is signing up someone for a service and billing some account.
No one is going to select and memorize a strong password for every website they use.
Its actualy not hard to do, just requires a little bit of effort on the part of the user to "change over" their whole password system.
1. Start with a "complex" base for a password, something with various character types that you can remember -- along the lines of the first letters of a phrase. (My Birthday Is In December. => m3iz1N12.)
2. Then for each application specific password append, preprend or insert (in a systematic way that again, you'll remember later on) something unique to that service. Probably best to stick to a character limit for easy recall. Maybe even include a numeral for its "version number" (explained below)
eg. Facebook might be m3iz1N12. + F4Ce + 10
Result: you have a unique strong password for each service you subscribe to, with a systematic method for remembering it if you forget (base + your indentifier scheme) without having to rely on security questions.
Then when it comes time to update your password, which you should be doing periodically anyway, you can increment the "version number" while keeping your password similar to but yet still "strong"
Of course this is a moot point if the service gets breached, but it shouldn't stop you from having good passwords of your own.
I get the whole "he should do his job thing," but I'd agrue that he is. His job is to improve/develop that company's infrastructure. It doesn't matter that he doesn't have ALL the knowledge in his brain to do this from scratch. He's researching using the tools he has avaiable and one of those tools is the knowledge base at slashdot.
Except unfortunately it seems everytime someone asks the slashdot "community" for help with anything. They immediately get thrown under the bus for asking the question in the first place. So much for the "community" and helping colleagues in the field.
Really? If you can afford $75/month, you can afford it with taxes.
I don't really agree with that logic.. If you can afford 75, can you afford 80.. then if you can afford 80, can you afford 85? 90... 95? etc.. to infinity
Slashdot Mirror
Trouble is once they have access to that garbage email account, they can sign you up for services using it along with other easily had information like your birthday, place of residence, etc.. And a lot of times they don't even have to get all of it right, comanies don't double check it, all they're interested in is signing up someone for a service and billing some account.
No one is going to select and memorize a strong password for every website they use.
Its actualy not hard to do, just requires a little bit of effort on the part of the user to "change over" their whole password system.
1. Start with a "complex" base for a password, something with various character types that you can remember -- along the lines of the first letters of a phrase. (My Birthday Is In December. => m3iz1N12.)
2. Then for each application specific password append, preprend or insert (in a systematic way that again, you'll remember later on) something unique to that service. Probably best to stick to a character limit for easy recall. Maybe even include a numeral for its "version number" (explained below)
eg. Facebook might be m3iz1N12. + F4Ce + 10
Result: you have a unique strong password for each service you subscribe to, with a systematic method for remembering it if you forget (base + your indentifier scheme) without having to rely on security questions.
Then when it comes time to update your password, which you should be doing periodically anyway, you can increment the "version number" while keeping your password similar to but yet still "strong"
Of course this is a moot point if the service gets breached, but it shouldn't stop you from having good passwords of your own.
for fucks sake yes. I called my doctor the other day to have them fill out a form and they "don't do email". wtf
I get the whole "he should do his job thing," but I'd agrue that he is. His job is to improve/develop that company's infrastructure. It doesn't matter that he doesn't have ALL the knowledge in his brain to do this from scratch. He's researching using the tools he has avaiable and one of those tools is the knowledge base at slashdot. Except unfortunately it seems everytime someone asks the slashdot "community" for help with anything. They immediately get thrown under the bus for asking the question in the first place. So much for the "community" and helping colleagues in the field.
im not sure spell check would have picked up on "tam" http://dictionary.reference.com/browse/tam
, maybe the company will finally implode and let other OSes get a greater market-share.
newsflash, other OS's are already gaining market share.... http://marketshare.hitslink.com/report.aspx?qprid=9
Of course the downside is that you'd both need Macs.
Why is that a downside? at least its a solution that would actually work..
Really? If you can afford $75/month, you can afford it with taxes.
I don't really agree with that logic.. If you can afford 75, can you afford 80.. then if you can afford 80, can you afford 85? 90... 95? etc.. to infinity