Re: [Full-disclosure] INSECT Pro 2.5 Release - Web scanner tool

2011-04-01 Thread rdsears
Well correct me if I'm wrong, but the whole premise of an un-regulated forum is for people to collaborate on opinions, even if they don't necessarily agree. You clearly didn't like the comments directed toward the INSECT devs, so aren't you 'wasting your time' by replying to them yourself?

Re: [Full-disclosure] NiX - Linux Brute Force 1.0.3 update has been released

2010-11-19 Thread rdsears
Would you care to offer what particular tests you did to compare your tool to Hydra? Just curious. Ryan On Nov 19, 2010, at 6:52 PM, n...@myproxylists.com wrote: There are several fixes done in this release compared to the 1st version. It is encouraged to upgrade to the latest version.

Re: [Full-disclosure] NiX - Linux Brute Forcer (the beast) has been released!]]

2010-11-13 Thread rdsears
In all fairness I do use proxychains for all of my proxy randomization and all that kind of stuff if I need it. That way it's consistent regardless of what I throw at it, even tools without random proxy chaining like nmap and hydra. Good job coding it though, I can't imagine that was easy. Ryan

Re: [Full-disclosure] Filezilla's silent caching of user's credentials

2010-10-11 Thread rdsears
I mean it's a nice thought, but the steps to get something like that indexed are quite silly. You would have to have your webserver indexing your application data, which is clearly a HUGE mis-configuration on their part. I personally don't care because I don't know if it's really going to do

Re: [Full-disclosure] New tool for pentesting

2010-09-17 Thread rdsears
Seriously. The only reason CANVAS and IMPACT are still used is because of the 0-days that come packaged with them. Metasploit if far superior not only in exploitation, but post exploitation, persistance, networking pivioting, and just generally being a badass! Can ANYTHING really compare to

Re: [Full-disclosure] Windows' future (reprise)

2010-05-15 Thread rdsears
And what of the pass the hash group of attacks, not to mention the insecure hashing to begin with? Combine that with token manipulation and process migration and you have a very deadly combination to almost any windows network that you don't see anywhere else. Exploiting windows networks