Skip to content

Instantly share code, notes, and snippets.

@nmors

nmors/gist:742571c07435fa8e37125dbfec86eb3c

Forked from jesusprubio/gist:8f092af4ca252e252eab
Created September 1, 2016 01:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save nmors/742571c07435fa8e37125dbfec86eb3c to your computer and use it in GitHub Desktop.
Save nmors/742571c07435fa8e37125dbfec86eb3c to your computer and use it in GitHub Desktop.
Download ZIP
Proposal: A Node.js penetration test framework
Raw
gistfile1.md

Proposal: Node.js penetration test framework

Hi guys! Since I started to write Bluebox-ng I've been tracking the different security projects I found written in Node.js. Now we've published the first stable version we think it's the right moment to speak among us (and, of course, everyone interested in it :).

Why?

  • I think we're rewriting the same stuff in our respective projects again and again. For example, almost any tool supports IPv6 because the functions we need are still not present in the Node core and the libraries I found (IMHO) were not enough.
  • There're different projects implementing exactly the same thing, ie: port scanners.
  • We're working in a too new environment, so we need to make it together.
  • Our 2 cents to make Node still more awesome. Now we have io.js whose main idea is to gain commiters.

To clarify: We've NO interest in keeping the project name or something similar, our only idea is to code in a bigger community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment