Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Ok maybe I am missing something but... (Score 1) 200

Ok. I'm still not seeing how this would be valuable. To compromise this wouldn't the following things need to be in place?
  1. Router is being configured via wireless.
  2. No encryption on the wireless signal (or signal encryption is known)
  3. Configuring the router via https (common).

So if I have WPA2 on and configure my router via a wire how would knowing my routers SSL key be all that valuable?

Comment Re:Methyl hydrate apocalypse averted? (Score 1) 223

Thats why we must strike first. If we extract all the Methyl Hydrate first then the earth wont have a chance to release it on us. Better yet we will set it on fire and burn it in its face. If we burn it all then there wont be any green house gasses to be released. Best way to prevent the apocalypse.


Um. Wait a minute.....


/sarcasm

Comment Re:There goes the Eternal September (Score 3, Informative) 193

(People won't be geting their Usenet through AOL anymore).

They already dont. If Eternal September hasn't ended by now then Usenet is screwed. According to Wikipedia article on eternal september:

On February 9, 2005, AOL discontinued newsgroup access through its service, which it announced on January 25, 2005.

Best start hunting the source of infection again.

Comment Operating System specific? (Score 2, Interesting) 181

The title says it is multi-platform but doesnt mention that anywhere in the article. So is this one that runs on CustomFW, Windows and Linux based ATMS?

To me it would seem better to create a system that would raise the "your-not-with-OUR-bank-so-we-can-stiff-you" charge (charge em 3.50 for the transation then send 2 back to the bank per normal). Slow but would make money over time if EVERY atm had your code.

Comment Re:Does anyone know... (Score 2, Insightful) 166

Well. This attack is used on the less robust TKIP protocol. AES is much stronger. Here is the break down (from my memory weakest to strongest):
  1. WEP
  2. WPA/TKIP
  3. WPA/AES
  4. WPA2/TKIP
  5. WPA2/AES

WEP Came first. It was one of those "oh we need security" bits. It's about what you would have on a wired network. Yea, no, not really. Broadcast != Hardwire so that quickly began being broken. Collisions were found. Time for something stronger

WPA came next but it was a bit advanced and all of these older machines didn't have really good processing in them and AES was a bit to intensive so the came up with WPA/TKIP. Lighter encryption but the old devices could pull it. WPA/AES came out around the same time and was stronger but the encryption had a bigger processing overhead.

Then WPA2 (802.11i) came about with further layers and was what really should have been from the start. Backwards compatibility was a problem here and key to adoption. TKIP stayed as some machines didn't take AES very well. WPA2+AES was the real place most will tell you to be. The whole multiple things was just getting protection out there on a technology that was rapidly falling apart.

Here is an analogy. US went to war with nearly unprotected Humvees (WEP). They worked well and they did their job. But attackers just blew right through it. So in an effort to get things locked down they welded plates of metal on the Humvee (WPA) some machines could handle more (AES) some less (TKIP). The military went back and developed a new technology similar to the quick field fix and came up with the Armored Humvee (WPA2) with good protection all around and made it standard (802.11i). Still defeatable but it can take a lot more.

There. I'm sure it would have been easier to find a wikipedia article and link to that but I was bored.

Comment Re:evil gluten (Score 1) 83

It also is the dietary trend of the day.

Not quite. See we Celiac folk (myself included) who truly suffer take great offense to the "trend" notion. You know why? Becaue while more and more people are trying it out (to see if it will help) the disease actually exists. Its not a 'South Beach' or 'Atkins' fad when you are stuck doing it for the rest of your life. Please, cut us some slack or at least acknowledge that people may really suffer from something like this and are not just 'food fadsters'.

Comment Re:Do the users/sysadmins want to change? (Score 1) 720

Nay sir. They COULD care less. They have asked if we are going to upgrade. We have explained that we are out of money and they would need to learn the new system. They go, "Oh... Yea... not quite sure I want to learn the new system. Just wondered." See if they didn't ask then they COULDN'T care less. At this point they have just a little bit of care.

And yes I didn't actually mention they had asked. Just going with what came out.

Comment Do the users/sysadmins want to change? (Score 4, Insightful) 720

The thing with the businesses is CHANGE. See they have this software they know works with XP, Sysadmins who know XP front and back, users who are used to XP, zero in the buy-new-machines fund, and are looking to save money anywhere they can. To justify buying a new version of Windows might be hard since, despite its age, XP works.

Our university department is cash strapped right now and despite heavy discounts we will NOT be moving to 7 unless it comes installed on a computer. We might if we are lucky get it in the 2011 FY budget. Unlikely though. Our users are so used to the look and feel that they likely would balk at the 7 upgraded look, and ask us to put back in the "classic" look. Yes the Windows 2000 look. Not that new XP Luna stuff. 2000. Thats why we are not switching to 7 anytime soon. The users could care less and our administrators wont give us the money.

Plus, were a little lazy and dont want to reinstall all of those comptuers.

Comment How about a password to kill the machine (Score 1) 500

Instead of having a "secure" and "super secure" sections how about a third option: "nuke data." That way you give them the byebye data password (you have a hidden backup right?) and when they enter it in the data disappears. You could even have it go through and scramble the data. No real biggie there just trash some bits randomly then relock with an unknown password.

Scenario: You make a data encrypted area (heck make it the whole harddrive like TrueCrypt can) then backup the encrypted
Situation: You are forced to give over the password.
Solution: You give them the "nuke data" password.
Outcome: Encryption program reports that secure partition has been improperly modified and is corrupt. Now none of your passwords will work.

Officer: Ok smartie. Whats the decrypt password?
You: RickAstley (cause your "never gonna give you up". sorry bad joke ill show myself out)
Officer: Ok. lets try it. Hmm. It says that the partition is corrupt
You: ARE YOU SERIOUS! I go from having to show you my private data to not having it. Great. Thanks. Way to go.
Officer: Right. Not working here. What the REAL password.
You: The full decrypt was "1337Crypt" but if it is corrupt were both screwed
Officer: Yep still says corrupt. Cannot decrypt information. Well were both screwed I guess.

So the other question is would this make you just as guilty?

Slashdot Top Deals

It is clear that the individual who persecutes a man, his brother, because he is not of the same opinion, is a monster. - Voltaire

Working...