Originally posted by: Goosemaster
Originally posted by: Pepsi90919
Originally posted by: CZroe
Originally posted by: Pepsi90919
lol @ OP. blaming everybody but himself for his mistakes.
LOL dumbass can't read. "The OP" asked for nothing more than recovery software. Microsoft is to blame for malfunctioning software, not for the FTP ransacking that the workaround *predictably* led to.
I had the option to come in here and ask for recovery software without any "backstory" but I thought it would be entertaining to those "in the know" like me and a warning for those who don't know what can happen. Instead, I stepped into a schoolyard pissing ground where people have to keep experiences secret lest they be made fun of. Grow up!
If I were incompetant and admitted it, I'd probably have sympathy. I guess it's just impossible for someone competant to relate something like this. Strange that we should shut up and let it happen to people who really don't know better.
...and you continue to blame everything but yourself...
1. we don't need a warnign about IIS....it's implied:laugh: Hell they should put "black hat conference certified: HACKABLE" on there for sh!ts and giggles....
2. the error was yours. You leave an ftp wide open and it's your own damn fault. didn't know what you were doing? Not MS's fault. Many people run secure IIS servers. It's a bitch and you have to patch it like an ER patient that is bleeding out and isn't clotting, but it is doable, and many people have success stories to back that up.
3. many people including myself have given you great recommendations, and yet you continue to discuss this "backstory" as if you can some how vindicate yourself or place blame elsewhere. We KNOW that you are at fault.*
*= 4. We KNOW that you are at fault because...LOFl..AHAHAHHA...dude, because you are NOT "in the know"
:laugh:
"LOFl..AHAHAHHA" all you want, but you clearly only think that I'm not "in the know" because you too misinterpreted things.
#1. Nothing was hacked. The "warning" has nothing to do with IIS. It's not for people running FTP servers today (they SHOULD know better). It is for people who possibly have no Internet experience and may someday remember things like this when they do. I'm not even saying that they need to know not to leave an FTP with Read/Write access, I'm saying that they need to know other details like undeletable folders and how to spot strange activity.
#2. How can you say that I "didn't know what I was doing" when I knew exactly what I was doing AND the potential consequences BEFORE they happened (right down to the undeletable folders and warez couriers)? Yes, many people run secure IIS servers with success stories. I'm reporting a horror story, not an inability to operate IIS. I'm trained, certified and experienced. I was dealing with a problem that was likely due to corrupted ACL or security accounts database. It's a problem that persisted until the OS was reinstalled. I got all sorts of strange behavior, such as being able to log in only when accessing it through
ftp://localhost instead of the actual IP (should be interchangable if everything is working correctly) and later with the IP but only being able to log in from the PC running the FTP server (inexplicably denied to other clients). Even if those issues were not directly related to IIS, enabling anonymous Read/Write access was the only way I could get another PC logged in to the FTP remotely. It's unfortunate that I was left with no time to backup my FTP or set a different root folder but trying to get proper login credentials to work had wasted all the time I had. Sure enough, after reinstalling XP and recreating the FTP, everything worked as it should. The problems I was having were NOT user error. In case you haven't figured it out yet, the MS/IIS problems I complained of had nothing directly to do with someone accessing and deleting my FTP contents. When you blame me for the "problem," you picked the wrong problem. I NEVER complained of there being a "problem" with wide open FTPs being ransacked.
#3. That's just it. What you "know" is incorrect. Just like M4H went around on DailyTech telling everyone that I did this on a Windows 2000 Server machine and that I was "surprised (both statements are as wrong as can be). Yes, trolling like this is not like him but he did this totally unprovoked before I made even the first reply. This goes to show that if you don't think an explanation is required to prevent rampant slander, you're wrong. If you thought that I'm doing this to protect my reputation from people within this thread, you're wrong.
#4. That's just fanning the flames. You read what you wanted to read to assert your superiority. I don't care if you have more real world experience, knowledge, certifications and really are superior (you could, I don't dispute it) but that doesn't make your interpretation of my level of competance correct. In fact, you're dead wrong.
. Oh one more thing. OWNED!!!!!!!!!11111111111 :laugh:
Facebook
Twitter