Home → Problems →

Arachni is running so long even with the latest version 0.4.1.3

Showing page 2 out of 2. View the first page

1. Support Staff 31 Posted by Tasos Laskos on 13 Mar, 2013 08:35 PM

   

   I logged in to the server you gave me, and I don't know how to put this in a way that won't make you want to hurt yourself, but all this time you were working the wrong package.

   All the systems you were using were 64bit ones but you kept downloading the 32bit package from http://downloads.arachni-scanner.com/nightlies/.

   Download the 64bit package and you'll be fine.

   • Edit

2. Tasos Laskos closed this discussion on 13 Mar, 2013 08:35 PM.

3. gopal.bansal1990 re-opened this discussion on 13 Mar, 2013 08:41 PM

4. 32 Posted by gopal.bansal199... on 13 Mar, 2013 08:41 PM

   

   Thanks Tasos,

   I am downloading the 64 bit package and will let you know if i find out any issue.

   • Edit

5. Tasos Laskos closed this discussion on 13 Mar, 2013 08:43 PM.

6. gopal.bansal1990 re-opened this discussion on 13 Mar, 2013 08:51 PM

7. 33 Posted by gopal.bansal199... on 13 Mar, 2013 08:51 PM

   

   Thanks Tasos,

   Its working fine, Hope limit-count command will work on this build.

   Thank you so much!!!!

   • Edit

8. Support Staff 34 Posted by Tasos Laskos on 13 Mar, 2013 08:53 PM

   

   No worries, glad you got it working.

   • Edit

9. Tasos Laskos closed this discussion on 13 Mar, 2013 08:53 PM.

10. gopal.bansal1990 re-opened this discussion on 18 Mar, 2013 01:59 PM

11. 35 Posted by gopal.bansal199... on 18 Mar, 2013 01:59 PM

    

    Hi Tasos,

    We are able to execute the ./arachni command manually but when we are trying to execute the same command from php code, we are getting the below error; it would be great if you can also please help us on this:

    /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler.rb:272: warning: Insecure world writable dir /var/www in PATH, mode 040777
    /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/source/git.rb:176:in `rescue in load_spec_files': git://github.com/Arachni/arachni-rpc-em.git (at master) is not checked out. Please run `bundle install` (Bundler::GitError)
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/source/git.rb:174:in `load_spec_files'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/source/path.rb:86:in `local_specs'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/source/git.rb:149:in `specs'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/lazy_specification.rb:52:in `__materialize__'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/spec_set.rb:88:in `block in materialize'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/spec_set.rb:85:in `map!'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/spec_set.rb:85:in `materialize'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/definition.rb:114:in `specs'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/definition.rb:159:in `specs_for'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/definition.rb:148:in `requested_specs'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/environment.rb:18:in `requested_specs'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/runtime.rb:13:in `setup'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler.rb:120:in `setup'
        from /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler/setup.rb:17:in `<top (required)>'
        from /var/www/arachni-1.0dev-0.4dev/system/usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:110:in `require'
        from /var/www/arachni-1.0dev-0.4dev/system/usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:110:in `rescue in require'
        from /var/www/arachni-1.0dev-0.4dev/system/usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:35:in `require'
        from /var/www/arachni-1.0dev-0.4dev/bin/../system/arachni-ui-web/bin/arachni:14:in `<main>'
    

    • Edit

12. Support Staff 36 Posted by Tasos Laskos on 18 Mar, 2013 02:11 PM

    

    Looks like you're running system/arachni-ui-web/bin/arachni directly, is that right?

    • Edit

13. 37 Posted by gopal.bansal199... on 18 Mar, 2013 02:32 PM

    

    There is a "system()" function in PHP which we are using to run arachni on linux console:

    $cm2="./arachni --mods=sqli_* http://testphp.vulnweb.com/ --report=xml:outfile=gopal_jorxn2ys_58_1_autarachni_Sql.xml";

    $abc2=system($cm2);

    • Edit

14. Support Staff 38 Posted by Tasos Laskos on 18 Mar, 2013 02:43 PM

    

    Still, that doesn't tell me what script you're executing, what dir are you running it from?
    What does system( 'pwd' ); say?

    • Edit

15. 39 Posted by gopal.bansal199... on 18 Mar, 2013 02:46 PM

    

    Here is the output of system('pwd'):

    command is: pwd
    results is: /var/www/arachni-1.0dev-0.4dev/bin

    • Edit

16. Support Staff 40 Posted by Tasos Laskos on 18 Mar, 2013 02:56 PM

    

    This is an environment issue and I've no idea how to help you fix it but could you try running:
    php5 -r "system( './arachni -h' );"

    From the same dir but from the command-line rather than via Apache.

    • Edit

17. 41 Posted by gopal.bansal199... on 18 Mar, 2013 03:04 PM

    

    This command is working on command line with the below warning:

    /var/www/arachni-1.0dev-0.4dev/system/gems/gems/bundler-1.3.4/lib/bundler.rb:272: warning: Insecure world writable dir /var/www in PATH, mode 040777 WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.7.8

    • Edit

18. Support Staff 42 Posted by Tasos Laskos on 18 Mar, 2013 03:09 PM

    

    The Nokogiri warning isn't a problem, the first one though could be.
    I've very little experience with Apache's intricacies so you'll need to ask someone else as to why the CLI PHP interpreter works but the same thing explodes when running it via Apache.

    I suggest you ask at StackOverflow.

    • Edit

19. Tasos Laskos closed this discussion on 18 Mar, 2013 03:09 PM.