Joost Hoogendoorn cyberjoost

In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:

http://techcrunch.com/2007/08/11/facebook-source-code-leaked/

It became a big deal:

http://www.techmeme.com/070812/p1#a070812p1

The two files are index.php (the homepage) and search.php (the search page)

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

A reader asked me over email recently:

Have you posted anything or had any thoughts on Ghash.IO situation?

Nothing on this. I think it's just early volatility in bitcoin space. Some company (CEX) got serious about making a private mining farm and made a whopping share. Others will follow soon.

The dirty little secret of the blockchain is that it's not secure until increasing the hashrate by even 1% is an enormous economic feat. Currently it's not impossibly expensive to build your own farm with significant share - therefore the network is not very theoretically secure. Even if every existing pool had no more than 10%, you can't be sure that some guy does not unleash enormous hashing power at once and reverts some transactions.

When more companies start building private farms (and they will, it's the only cost-efficient way to mine; individual miners will soon disappear), you'll see more even distribution of the hashrate, but most importantly, the growth of hashrate will get slower. Because the slo

superfish.pem contains:

the Superfish certificate as found by both Chris Palmer and Matt Burke;
the encrypted private key as found by Karl Koscher.

$ openssl x509 -in superfish.pem -text
Certificate:
    Data:
        Version: 3 (0x2)

	#!/bin/env python

	'''This is a script which runs an MTR (matt's traceroute)
	against a target hosts - meant to be triggered by a
	smokeping alert. Output is emailed and saved to log.'''

	import argparse, datetime, subprocess, smtplib
	from email.mime.multipart import MIMEMultipart
	from email.mime.text import MIMEText

	# source : http://code.google.com/p/natvpn/source/browse/trunk/stun_server_list
	# A list of available STUN server.

	stun.l.google.com:19302
	stun1.l.google.com:19302
	stun2.l.google.com:19302
	stun3.l.google.com:19302
	stun4.l.google.com:19302
	stun01.sipphone.com
	stun.ekiga.net

	# Reverse proxy for Shinken 2.0.x on Debian Wheezy
	# Place this file under /etc/nginx/sites-available
	# Update your server_name
	# Don't forget to enable the config and reload nginx
	# Enjoy ^^
	server {
	# IPv4 support
	listen 80;
	# IPv6 support
	listen [::]:80;

	#!/usr/bin/env ruby

	require 'rubygems'
	require 'json'
	require 'pp'
	require 'open-uri'
	require 'cgi'
	require 'httparty'

	affiliate_id = 'olenaw-20'

	#ifndef UNICODE
	#define UNICODE
	#endif

	#include <Windows.h>
	#include <string.h>
	#include <stdio.h>
	#include <Psapi.h>

	#!/usr/bin/perl

	# http://www.mail-archive.com/[email protected]/msg04048.html

	# this script would be run when smokeping detects some loss. The
	# smokeping trigger could look like:
	#
	# +highLossTwice
	# type = loss
	# pattern = >70%,>70%