Peter Wallhead peterwallhead

Basecamp was under network attack

The attack detailed below has stopped (for the time being) and almost all network access for almost all customers have been restored. We're keeping this post and the timeline intact for posterity. Unless the attack resumes, we'll post a complete postmortem within 48 hours (so before Wednesday, March 26 at 11:00am central time).

Criminals have laid siege to our networks using what's called a distributed denial-of-service attack (DDoS) starting at 8:46 central time, March 24 2014. The goal is to make Basecamp, and the rest of our services, unavailable by flooding the network with bogus requests, so nothing legitimate can come through. This attack was launched together with a blackmail attempt that sought to have us pay to avoid this assault.

Note that this attack targets the network link between our servers and the internet. All the data is safe and sound, but nobody is able to get to it as long as the attack is being successfully executed. This is like a bunch of people

	<?php

	/**
	* 1. create project at https://console.developers.google.com/project
	* 2. enable 'Analytics API' under 'APIs & auth' / APIs
	* 3. create 'NEW CLIENT ID' (OAuth client) under 'APIs & auth' / Credentials
	* i. select 'Service account'
	* ii. save generated key file to 'key.p12'
	* iii. remember CLIENT ID
	* 4. under GA account add 'Read & Analyze' access to newly generated email (access to GA Account not Property nor View)

	#!/usr/bin/env ruby
	# gem install sinatra --no-document
	# gem install github-markdown --no-document
	require 'sinatra'
	require 'github/markdown'
	set :port, 3000

	get '/' do
	<<-EOT
	<!DOCTYPE html>

	var json = {
	data: ['a','bunch','of','things']
	};

	var otherData = {
	things: [],
	madness: {}
	};

	json.data.forEach(function(data,index,array){

	import csv
	from django.core.management.base import BaseCommand, CommandError
	from django.core.exceptions import ValidationError, ObjectDoesNotExist
	from django.db.models.fields import FieldDoesNotExist
	from scour_server.nbi.models import Bridge

	class Command(BaseCommand):
	args = '<path>'
	help = ''

	public String multipartRequest(String urlTo, String post, String filepath, String filefield) throws ParseException, IOException {
	HttpURLConnection connection = null;
	DataOutputStream outputStream = null;
	InputStream inputStream = null;

	String twoHyphens = "--";
	String boundary = "***"+Long.toString(System.currentTimeMillis())+"***";
	String lineEnd = "\r\n";

	String result = "";

	I had this really small problem today. I wanted to migrate one of my small django apps to use postgres, just to make everything easy to manage. Sqlite3 is perfectly fine for the amount of load, however I am really much faster at administering postgres than I am on sqlite3. So I decided to migrate the stuff over.

	I tried a few approaches, but what ultimately worked the best and the fastest fo rmy particular problem was to do the following.

	Use original SQLITE3 connection in settings.py
	1. python manage.py dumpdata > dump.json

	(I read some things here about some options you can pass, at the end what just worked was the following)

	2. Change DB connection string in settings.py to POSTGRES

	import os
	import pytest

	from alembic.command import upgrade
	from alembic.config import Config

	from project.factory import create_app
	from project.database import db as _db

	import urllib2
	import re
	import sys
	from collections import defaultdict
	from random import random

	"""
	PLEASE DO NOT RUN THIS QUOTED CODE FOR THE SAKE OF daemonology's SERVER, IT IS
	NOT MY SERVER AND I FEEL BAD FOR ABUSING IT. JUST GET THE RESULTS OF THE
	CRAWL HERE: http://pastebin.com/raw.php?i=nqpsnTtW AND SAVE THEM TO "archive.txt"

	// 1. Go to page https://www.linkedin.com/settings/email-frequency
	// 2. You may need to login
	// 3. Open JS console
	// ([How to?](http://webmasters.stackexchange.com/questions/8525/how-to-open-the-javascript-console-in-different-browsers))
	// 4. Copy the following code in and execute
	// 5. No more emails
	//
	// Bookmarklet version:
	// http://chengyin.github.io/linkedin-unsubscribed/