slipangel

Not true. Can you imagine the economic impact if this stands as a case study on how lax security standards could be at large, trusted private institutions? That all it takes is one pissed-off employee with a cursory background in computer security to cause billions of dollars in damages and rampant fear?

It's much easier to address public fears with an easy scapegoat than to owe up to the overall frailty of network-driven industry. Could you imagine the cost of creating "the TSA of networks belonging to important private entities?"

As an auto enthusiast, I generally feel "yucky" after surveying the comments and feedback following a Tesla press release. C&D and MotorTrend generally bias hard for anything American made, which is fine and par for the course. My discomfort comes from the feeling that journalists are making the Model S out to be a competitive alternative to a high performance automobile, which it is not.

A Model S can't make a single lap in anger around Mazda Raceway without the software putting it in limp mode to prevent heat build up from causing permanent damage. A half-day jaunt through twisty mountain roads is absolutely out of the question. It is a car that can drag race from a stop, hit a freeway on-ramp with some gusto, and give you carbon-free credentials the rest of the time.

No one shopping for an M3, 911, or AMG product who actually intends to use them for their performance is cross-shopping a Model S as a like-for-like option, but the press consistently paints the picture that Tesla is a gas-free alternative or even superior to current offerings. I don't intend to degrade what it is, because it is a marvel of modern business, politics, and a little engineering that this car exists. I simply feel gross when I see how much hype puts it up for the Model S being something it isn't.

sudo chown -R myname:myname /

Learned: Learning on the job as you hack away on problems is great, but recognize that it's one part enthusiasm and one part risk management. Also learned to never try anything on the command line that wouldn't want to see pulled from my bash history and stuck on the breakroom fridge. Also learned to cope with humiliation well.

The a248 cert is used for all SSL requests for properties delivered over Akamai's non-ssl network. It's useful to be able to serve SSL requests even if the cert doesn't have a the hostname in question on it.

Regarding the cipher sneering below: Akamai's default settings probably err on the side of acceptance. Not all of their customers are Amazon.coms - mom & pop ecommerce are unlikely to do anything that would cause a visitor's SSL connection to fail, and changing the ciphers back to the high-acceptance settings would increase their cost of implementation per cert. I'm guessing they manage more than a few of those.