markt

I just can't wait for all of this to be over so we can compare the elaborate and unusual lengths we went to try to be FTF! If I could be sure that New England wouldn't be seeing another cache (unlikely, I know) ...

I guess my use of the word hacker was a little premature. I also saw how the urls were constructed, and tried replacing the id's just for grins for a couple of other caches. It didn't work, as others pointed out. It wasn't a "backdoor" - it was a goof on the part of the site admin. Since I hadn't seen such a (simple) trick work, I assumed the "hacker" might have gotten into the database server. Not all that unreasonable, since if they're using Active Server Pages (.asp), then they're using Microsoft IIS. And so it's not a far leap to assume they're using SQL Server. And, there have been a number of holes plugged recently with that product. I figured someone used one of the vulnerabilities to get it. Alas, none of that is true, apparently. Just some fat-fingering on the part of the website admins.

I do agree that censoring the issue is in bad taste. But, sadly, it's their server and they can do what they want with it, including wiping out embarassing info. I'm sure they know it'll be discussed all over the place (and probably the newspapers too). If they don't, then they really do have their heads in the sand.

I agree they did mess up, and they should make good on it. But it's never done before, commercially, and maybe they were hacked. A couple unforunate incidents, but I wouldn't swear off their products because of it. I'm just curious how the hacker got in

Wow - if only they worked it out with the homeowner first, I'd think Magellan was trying to sucker in and nab some hackers!

Val, See you there! C'mon MA! -mark

Does anyone have this that they don't want anymore?