On 07/26/2011 11:12 AM, Andres Riancho wrote: > Steve, > Ahh, that's good information! So we can do any of the following: > * Don't use multiprocessing for those platforms, use the classic > "threading" model > * At the beginning, check for those OS and stop if OS dependency of > "all but Solaris, AIX, openBSD and FreeBSD < 7.2" is not met. > > The first one seems more complex, but it all depends on how many users > don't meet our that req.
If you look at the patch to sqlmap, that's basically how I changed it. They already had a single threaded implementation, just switched to that if "import multiprocessing.synchronize" fails. > > Where did you get this info from? A bunch of places. :-) This link claims FreeBSD 7.2 and later work: http://www.velocityreviews.com/forums/t716510-freebsd-and-multiprocessing.html The bug linked in the error message says openBSD and FreeBSD <=7.0 are broken: http://bugs.python.org/issue3770 The python configure file say AIX and Solaris are borken. All of these should fail on importing multiprocessing or multiprocessing.synchronize, so it's easy to test for. Note that FreeBSD 7.1 and earlier are out of support, so usage base should be fairly low. 7.1 went EOL on Febuary 28, 2011 http://security.freebsd.org/ Does anyone actually use openBSD, AIX, or Solaris? ;-) -- | Steven Pinkham, Security Consultant | | http://www.mavensecurity.com | | GPG public key ID CD31CAFB | ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
