Sam Kozin skozin

This is a mix between two sources:

basically the first resource is great but didn't work for me: I had to remove the trailing "/*" in the resource string to make it work. I also noticed that setting the policy on the source bucket was sufficient. In the end these are the exact steps I followed to copy data between two buckets on two accounts

Basically the idea there is:

we allowe the destination account to read the source bucket (in the console for the source account)
we log as the destination and start the copy

Notes:

Text in [[ ]] are the internal libuv function call.
Text in {{ }} are the Node functions that are affected.
Text in ( ) are notes about what is happening.
While the Windows event loop has minor variations, I don't believe any of those affect Node.

On process.nextTick():

Introduction

Here is a collection of tips and tricks I've picked up about doing performance analysis on Node. Included is a build script that should get a base install of Ubuntu fully functional and ready for all the things we'll be going through.

The script pulls a lot of code from the latest master of each repository. So it's possible that something may fail, but to date I haven't had any issues.

First, go ahead and run the script. Then go take a nice long break. It'll

Verify and Repair Disk Permissions via Terminal (Mac OS X)

Verify Permissions

diskutil verifyPermissions /

Repair Permissions

diskutil repairPermissions /

Screencapture and animated gifs

I say "animated gif" but in reality I think it's irresponsible to be serving "real" GIF files to people now. You should be serving gfy's, gifv's, webm, mp4s, whatever. They're a fraction of the filesize making it easier for you to deliver high fidelity, full color animation very quickly, especially on bad mobile connections. (But I suppose if you're just doing this for small audiences (like bug reporting), then LICEcap is a good solution).

Capturing (Easy)

Launch quicktime player
do Screen recording

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.

	"""
	Python implementation of PKCS #7 padding.

	RFC 2315: PKCS#7 page 21
	Some content-encryption algorithms assume the
	input length is a multiple of k octets, where k > 1, and
	let the application define a method for handling inputs
	whose lengths are not a multiple of k octets. For such
	algorithms, the method shall be to pad the input at the
	trailing end with k - (l mod k) octets all having value k -

	#!/bin/bash

	# This script automatically sets the version and short version string of
	# an Xcode project from the Git repository containing the project.
	#
	# To use this script in Xcode, add the script's path to a "Run Script" build
	# phase for your application target.

	set -o errexit
	set -o nounset

	#!/bin/sh -e
	hostname=$1
	device=$2
	file=$HOME/.dynv6.addr6
	[ -e $file ] && old=`cat $file`

	if [ -z "$hostname" -o -z "$token" ]; then
	echo "Usage: token=<your-authentication-token> [netmask=64] $0 your-name.dynv6.net [device]"
	exit 1
	fi

	import java.io.FileDescriptor;
	import java.io.FileOutputStream;
	import java.io.IOException;
	import java.io.OutputStream;
	import java.io.PrintStream;

	public class HelloWorld{
	private static HelloWorld instance;
	public static void main(String[] args){
	instantiateHelloWorldMainClassAndRun();