Printable View
I consider the "new" AO to be the new members that join and spam our boards, or post in GCC exclusively. I could care less if someone posts malicious code.
I saw the post count and I figured he was brand spankin new. Turns out hes a year old. If you ask me, he should advertise in his sig only and start contributing to the forums.
Well, again, he did not spam. He was helping to contribute IMO. But that was in the grey line I suppose.
Ya know what, **** it. What do I know?
Am I the only one who noticed that the links are broken? Or is it just me?
Just the ones in his first post because they have extra punctuation. The links in his second post work.
rhfactor, thank you for sharing it with us.
Ahh, thanks muert0. Nice site there rhfactor, and I'm going to check out your program on my friend's box and see what I can find. :)Quote:
Just the ones in his first post because they have extra punctuation. The links in his second post work.
ps: I posted twice cuz the first one was my first post in these forums and I posted it in a wrong forum. Anyway, sorry all who get mad with my posts, wasn't my intention.
Btw, like cross said, I thought that here someone could use the tool. I made it cuz I worked some time as programmer and now I admin 3 webservers. Isn't only a hack tool. Like any sec scan, u can use it to evul or to protect yourself. Putting this tool in ur website is an easy way to check if u're FSO vulnerable, or CMD vulnerable, or REG vuln.
Anyway, my intention was to help and make someone use a FREE tool that NO ONE paid me to make.
ty all
Spyder32: no, this server sux :P
use a proxy and u probably will access the files, I dont know why but it works...
and SORRY AGAIN for those who HATE 2 posts in sequence, but I saw spyder msg after I sent my first msg
How come AO isn't like it was before? How come it changed to the "new" AO?
Last advice ( I don't wanna be called spammer again :P ):
to proctect your server against this stuff, change the permission of the FSO dll in system32 folder (I don't remember the file name, but I think that isn't too hard to search the web and find it). Protection against web prompt access, change cmd.exe permissions. I recommend to move all "dangerous" prompt appl to one specific folder and allow only adm to access it (net.exe, ftp.exe, cmd.exe, etc).
Anyway, before doing all these actions, better test all web folder permissions thru the tool, its good to see where you didn't applied the right permissions.
Main web folder must be well ACL configured.
Carefull with permissions in folders with write access (usually mdb or txt folders).
Is extremelly important the ACL configuration, otherwise your users can destroy your host.
If I said some **** (Im not talking about my english, I know that sux), if I'm "spamming", lemme know. I do my best.
;)