Why, oh WHY don't I have moderator points today ?????

You realize that the Apple Airport line supports RADIUS authentication, right?

All that said... The way I'd do it - to make support easy AND keep things secure - is a completely open WiFi access point. No encryption, no passwords required.

The trick is, the access points would only have one destination available - the VPN concentrator. Simple. Enable AES-256 on the VPN concentrator, and you're in business.

Sniff all you want - we'll make more. End users would connect to the VPN the same way from home or from the office WiFi. Easy, cheesy, and keeps the distinction between working at the office and remotely that much smaller.

... then it's between him & Apple. If Apple chose to put his picture up on their website with a huge "DON'T HIRE THIS MAN" banner, then that's between this gentleman & Apple.

By calling him out - publishing his name, social network information, pictures, birthday, etc - Gizmodo is really piling it in. They're making sure - in no uncertain terms - that he is completely & thoroughly embarrassed, humiliated and blackballed from Silicon Valley.

Why? I'm not saying it's illegal, I'm just saying that all it does is make a bad situation worse for this guy.

Yeah, he left the phone behind (if the story's 100% accurate..) Yeah, he works for Apple. But there's no reason to call it out other than just to be mean. ... and that's all this was. Just mean.

You know, I find that completely over-the-top.

If the story is accurate, then what's the point of exposing the poor sod's name?

What purpose does that serve? The guy's obviously had a rough week; why pile on and make it worse?

It's likely that he's going to be terminated (from his employment, not physically), if he hasn't been already. I'm sure there's some "handling company materials" guideline or somesuch on the books at Apple that will be enforced.

So why expose him publicly?

I don't get it. This just seems like nonsense to me.

Thank you for backing me up. This was absolutely a problem, and I spent many, many, many nights with the engineers replacing the "bad" CPUs with Sombra modules. p/n 501-6009's.... over a thousand of 'em.

The "cosmic rays" thing sounds like a joke, but the Sun engineers really explained it well (once they admitted something was going on) - it makes perfect sense and described the problem to a T.

Sounds a whole lot like the e-cache parity errors in the Sun UltraSPARC-II processors.

If you were never affected by that, consider yourself a lucky person.

particle-caused bitflips are very much real.

It's still great to see the providers bootstrapping DNSSEC. We need more of them onboard before you see widespread adoption.

I have a feeling you're going to see DNSSEC explode in a big way soon .... Comcast isn't the only ISP implementing it.

Verizon will unlock your phone as well. Both my and my wife's BlackBerry Storms are unlocked. By Verizon. No different than any other subsidized phone from any other US carrier ....

.. of course, a phone with dual radios such as the BlackBerry Storm, Samsung Saga, HTC Ozone, HTC Touch Pro2, etc. will work anywhere. My BB Storm works here in the US, in Europe, in the Caribbean, just about everywhere ...

It's the other way around.

CDMA's air interface is quite efficient, actually.

So efficient, in fact, that the 3GPP's 4G standard (you know, LTE, Long-Term Evolution) is much, much more CDMA-like than TDMA-based GSM. (CDMA and LTE are both spread-spectrum technologies -- GSM/TDMA divide signals on a carrier frequency based on timing.)

Keep in mind that the cdmaOne product family is what's not being evolved any further --- the actual air interfaces developed under the CDMA banner are really the path forward. What's being 'killed off' is the TDMA-type technology that underpins GSM.

That would be Columbia. We lost Challenger just 73 seconds after she lifted off.