PUMPKIN YOU INSENSITIVE CLOD!

Second!

First things first- all these replies "then I'd come back and see the result".

Let's just make sure we can come back, shall we?

I know that one of the options IMPLIES we can come back... but maybe it's a trick to get a hell of a lot of you out of the way!

Me too! I don't even own a PS3 and I want to buy one... just to see what Sony would do.

What grounds could they have against me if I own a bypass device without owning the device for which to bypass? :-)

But in the end, I'm too lazy, and cheap. *sigh*

I actually just recently had some rodents- either mice or chipmunks- chew up the brand new wiring I had just replaced in my trailer. I was less than thrilled.

I wasn't sure if they were attracted to it for bedding material, could "smell" the copper inside, or what. I guess this makes a whole lot more sense. On top of the gaping holes in the wiring, when it shorted out it blew a bulb or two making troubleshooting all the more painful after I traced and patched the wiring. I thought I had more breaches, but it was just a dang 'ole bulb. ;-)

I am going two factor now- I have declared war on the rodents and I'm armoring my trailer wiring.

I know this is only slightly on topic- but how was this registration found? Did they have to pay money to search the system?

What if I wanted to just go searching for a term? Or for all terms registered by a company? What stops people from doing that?

Exactly- phrased differently- "A vulnerability actively being exploited in the wild was patched".

Granted, some of those actively exploiting it were the owners of the devices... but hey. You seriously don't know if it was being exploited by others for financial gain. If they were that good, you'd never know. I'm all for patching the vuln.

Reality check. To quote the Italian Job:

"If there's one thing I know, it's never to mess with mother nature, mother in-laws and, mother freaking Ukrainians."

I haven't seen anyone post this yet: http://trinityhome.org/

Update it prior to write protecting it, and assuming you can boot those machines from USB as well, boot them and go to town. It has saved many a friend/family machine I have been forced to support for free.

Thank you. I read that and did a double take. I thought we were moving towards sandboxing the heck out of these things to keep them from accessing *stuff*.

I suppose it depends on how it's implemented, and I will admit I have read precisely _nothing_ on it.

But we all know how these things have historically played out... bleh.

So you're the one who created that dip in the stock market, eh?

I use an Alpha running Debian 5 under my desk. I think it was new in 1997? And quite expensive. I put all my SCSI disks into it and it's my SSH/file server. I also use it for other random things like TFTP and a quick HTTP server in a pinch. I recently did a Kerberos case study for a customer on it. Not so much for anything to do with compiling, but it's still running nicely otherwise. It was a science project to upgrade the RAM from eBAY considering it only had 32MB of RAM when I acquired it from my cousin (who is also a hardware aficionado and ran many a project off it for years). I got it up to 512MB after lots of research, tweaking and trial and error. Most of the guys at work still give me lots of crap about the dinosaur under my desk but a few of them give a nod to the good 'ol days. I just can't let it go.

What if the unintended negligence is both coming and going? A less technical user has an open Linksys at home, and brings their laptop somewhere and automagically joins this other open Linksys? Now you can blame both, or neither- or maybe the user with the laptop twice over since they are to blame both and home and on the road... ;-)

Well to be fair... it's camouflaged as a current generation iPhone to fit in during normal activities- not under scrutiny. Once you remove the faux case all bets are off.

Thanks- I almost snorted stir fry out my nose. Hard to do, to be sure, but I laughed that hard. :-)