Maik Ellerbrock ellerbrock

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.

Use these rapid keyboard shortcuts to control the GitHub Atom text editor on Mac OSX.

Key to the Keys

⌘ : Command key
⌃ : Control key
⌫ : Delete key
← : Left arrow key
→ : Right arrow key
↑ : Up arrow key

React (Virtual) DOM Terminology

In React's terminology, there are five core types that are important to distinguish:

ReactElement / ReactElement Factory
ReactNode
ReactComponent / ReactComponent Class

React Elements

Auto-deploying built products to gh-pages with Travis

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

Create a compile script

You want a script that does a local compile to e.g. an out/ directory. Let's call this compile.sh for our purposes, but for your project it might be npm build or gulp make-docs or anything similar.

The out/ directory should contain everything you want deployed to gh-pages. That almost always includes an index.html.

With Docker 1.8.0 shipped new log-driver for GELF via UDP, this means that the logs from Docker Container(s) can be shipped directly to the ELK stack for further analysis.
This tutorial will illustrate how to use the GELF log-driver with Docker engine.
Step 1: Setup ELK Stack:
- docker run -d --name es elasticsearch
- docker run -d --name logstash --link es:elasticsearch logstash -v /tmp/logstash.conf:/config-dir/logstash.conf logstash logstash -f /config-dir/logstash.conf
- Note the config for Logstash can be found at this link
- docker run --link es:elasticsearch -d kibana
Once the ELK stack is up now let's fire up our nginx container which ships its logs to ELK stack.

LOGSTASH_ADDRESS=$(docker inspect --format '{{ .NetworkSettings.IPAddress }}' logstash)
`docker run -d --net=host --log-driver=gelf --log-opt gelf-address=u

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

	/** @jsx React.DOM */

	var STATES = [
	'AL', 'AK', 'AS', 'AZ', 'AR', 'CA', 'CO', 'CT', 'DE', 'DC', 'FL', 'GA', 'HI',
	'ID', 'IL', 'IN', 'IA', 'KS', 'KY', 'LA', 'ME', 'MD', 'MA', 'MI', 'MN', 'MS',
	'MO', 'MT', 'NE', 'NV', 'NH', 'NJ', 'NM', 'NY', 'NC', 'ND', 'OH', 'OK', 'OR',
	'PA', 'RI', 'SC', 'SD', 'TN', 'TX', 'UT', 'VT', 'VA', 'WA', 'WV', 'WI', 'WY'
	]

	var Example = React.createClass({

	function Foo(who) {
	this.me = who;
	}

	Foo.prototype.identify = function() {
	return "I am " + this.me;
	};

	function Bar(who) {
	Foo.call(this,"Bar:" + who);

	========================================== ==========================================
	TMUX COMMAND WINDOW (TAB)
	========================================== ==========================================

	List tmux ls List ^b w
	New -s <session> Create ^b c
	Attach att -t <session> Rename ^b , <name>
	Rename rename-session -t <old> <new> Last ^b l (lower-L)
	Kill kill-session -t <session> Close ^b &

	#!/bin/sh
	set -x
	set -e
	#
	# Docker build calls this script to harden the image during build.
	#
	# NOTE: To build on CircleCI, you must take care to keep the `find`
	# command out of the /proc filesystem to avoid errors like:
	#
	# find: /proc/tty/driver: Permission denied