sinn3r d45cdd61aa Resolve #4507 - respond_to? + send = evil ... Since Ruby 2.1, the respond_to? method is more strict because it does not check protected methods. So when you use send(), clearly you're ignoring this type of access control. The patch is meant to preserve this behavior to avoid potential breakage. Resolve #4507		2015-01-02 13:29:17 -06:00
..
aix	Handle exception in brute force exploits	2014-11-18 12:17:10 -08:00
android	fix msftidy warnings	2014-12-12 13:16:21 +01:00
apple_ios	Differentiate failed binds from connects, closes #4169	2014-11-11 14:59:41 -06:00
bsdi/softcart	Fix up comment splats with the correct URI	2014-10-17 11:47:33 -05:00
dialup/multi/login	Fix up comment splats with the correct URI	2014-10-17 11:47:33 -05:00
firefox/local	Fix up comment splats with the correct URI	2014-10-17 11:47:33 -05:00
freebsd	Don't allow 127.0.0.1 as SRVHOST	2014-10-31 08:19:15 -05:00
hpux/lpd	Fix up comment splats with the correct URI	2014-10-17 11:47:33 -05:00
irix/lpd	Fix up comment splats with the correct URI	2014-10-17 11:47:33 -05:00
linux	Resolve #4507 - respond_to? + send = evil	2015-01-02 13:29:17 -06:00
multi	Land #4440, git client exploit from @jhart-r7	2015-01-01 13:18:43 -06:00
netware	Fix up comment splats with the correct URI	2014-10-17 11:47:33 -05:00
osx	code style	2014-12-11 23:30:20 +01:00
solaris	Handle exception in brute force exploits	2014-11-18 12:17:10 -08:00
unix	Do minor cleanup	2014-12-26 11:24:02 -06:00
windows	Resolve #4507 - respond_to? + send = evil	2015-01-02 13:29:17 -06:00