Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:There's a bigger issue here (Score 1) 238

The whole point is not eliminating "whole sections of society". That's exactly what this is about. If we refuse to vaccinate, we endanger those that cannot be vaccinated. Because the same group also cannot participate in a potential cure, for exactly the same reasons.

If these people could only endanger themselves, I'd say more power to them. Don't get vaccinated, but at least then have the decency to die peacefully when you get infected. If that was the whole story, I would not mind it. Not one bit. I'm all for idiots and assholes removing themselves from the gene pool. We, as society, can only benefit from it.

So technically, I would actually be for the removal of a section of society... albeit by their own doing, not mine.

The problem is that they don't just endanger themselves, but others too. It's a bit like drunk driving. If they could only kill themselves, all I would do is make sure they have enough to ensure a speedy delivery. Unfortunately they rarely die alone.

Comment Re: There's a bigger issue here (Score 1) 238

Ok, lemme rephrase that: There's a shortage of work that would be paying a wage.

And yes, you're absolutely right. Demand creates jobs. I've been saying this for ages, and every single time without fail I get shouted down that jobs are created by employers. But to employers, the job he creates is the necessary evil he would gladly go without if he could. Because "creating" a job means expense for him, not revenue.

I create a job if I want to buy apples. I create that job for the guy picking them. I create a job by wanting a new computer. I create a job by wanting to spend an evening at a bar. Ok, not a whole job, but a fraction thereof at least. If for nobody else, than for the owner of the bar who can keep the bar running because I spend my evening and my 100 bucks there.

And that only works if people have money to spend. But that's a different topic. What's left is that yes, there is work to be done. But pressing people to do it without a wage only creates even more pressure on wage earners who would now have to compete with these people forced into work. And if you tell me that "this would only apply to work nobody else wants to do" I have one sentence for you:

"H1B visa are just for jobs that we cannot fill with domestic workers"

Comment Re:Reality is... (Score 1) 191

No, My Gentle Fool, there isn't. It is entirely possible that 1-2-3-4-5 could be _Everybody's_ Password.

You've missed my point entirely. "12345" is the fifth numeric password an attacker would try (after "1", "12", "123", and "1234"). It doesn't matter how securely you store it or how long each guess takes, if an attacker has a reasonably high chance of guessing it by a mere educated guess.

Sure, you could lock the account after X guesses - But then you've just given me a trivial way of locking out the legitimate account-holder as well - Arguably, a lot of kids just out to raise some hell rather than seriously wanting to compromise your accounts would prefer that (applied on as large a scale as possible) than actually guessing the right password. "Oh, look, we just locked the entire Microsoft staff out of their own network, ha-ha!"

Any Password, hashed in any number of many ways repeatedly, and yet each one with a unique Time Stamp embedded and invisible, should do the trick.

That accomplishes nothing more than slowing down any brute force attempts. It certainly doesn't somehow magically make one of the top few million passwords more secure. Or, looked at another way, let's say you use such a horrendously complex hash that each guess takes a whole second. You've just handed any potential attackers a trivial on/off switch to DOS'ing (no leading "D" required) your site, as your poor server farm tries to keep up with just a handful of bad login attempts per second.

Time Stamps supposedly assigned to certain Alpha Decay Chains stuck out like three sore thumbs upon later Analysis.

Would you care to provide a link on how timestamped audit trails have anything to do with brute-force password cracking? It sounds like you've mixed up two separate concepts here. Yes, you can make an RTPS virtually tamper-proof; that doesn't have much in common with proving my identity to Facebook from a previously untrusted computer.

Comment So ... lemme get this straight.... (Score 4, Insightful) 337

You buy a superspecialawesome phone that is ultrasuper thin. Then you stick it into a phone case, returning it to the 3-4mm you had before.

So ... you have a phone with a crappy battery life because they can only include a paper thin battery pack, which has to be glued on and can't be exchanged "or it would get too thick", you accept that they take away your headphone jack for the sake of thinness, then you pay extra to put a case around it that returns it to brick size.

Let me spell that in a way that you people understand:

Comment Re:Complex Passwords (Score 1) 191

That's pretty much what someone did at an office I worked before.

They had a system where someone could call IT to say they forgot their password, which resulted in their account being locked and a new password was generated. What this person did was to call IT as the last thing before he went home, said he forgot his PW, had his account locked, then next morning he would show up, pick up his password "for the day", enter it, shredder the paper it was printed on, do his stuff, call IT at noon with a lost password...

He pretty much got away with it because he had the agreement with IT that they wouldn't cause a stir and he won't tell anyone about his trick to avoid memorizing passwords with ridiculous requirements.

Slashdot Top Deals

Some people carve careers, others chisel them.