duckythescientist

#!/usr/bin/env bash

worklog_dir="worklog"
editor="subl"

show_usage () {
	cat <<-EOF
	Create a diary text file by week in the $worklog_dir subdirectory
	by the year and month. Automagically adds a heading to the file
	and opens the file with $editor to the current* date.

duckythescientist

#!/usr/bin/env python3


import math

import numpy as np
import matplotlib.pyplot as plt

# def string_shannon(data):
#     '''Performs a Shannon entropy analysis on a given block of data.

duckythescientist

#!/usr/bin/env python3
# Or python2 

import itertools
import collections

# @profile
def get_primes(nMax):
    """Return a set of prime numbers under nMax

duckythescientist

#!/usr/bin/env python3

from heapq import heappush, heappop

median = None

heap_lower = []
heap_upper = []

len_lower = 0

duckythescientist

# https://stackoverflow.com/a/52465819
function readline_ANSI_escape() {
  if [[ $# -ge 1 ]]; then
    echo "$*"
  else
    cat  # Read string from STDIN
  fi | \
  perl -pe 's/(?:(?<!\x1)|(?<!\\\[))(\x1b\[[0-9;]*[mG])(?!\x2|\\\])/\x1\1\x2/g'
}

duckythescientist

#/usr/bin/env python3

import time
import threading
import functools

import tqdm


def long_running_function(*args, **kwargs):

duckythescientist

#include <stdio.h>
#include <stdint.h>
#include <stdlib.h>
#include <limits.h>
#include <string.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/mman.h>

duckythescientist

#!/usr/bin/env python2
import math

from pwn import *

"""
Read this: https://inst.eecs.berkeley.edu/~cs191/fa07/lectures/lecture22_fa07.pdf

I don't really know much about quantum computers.
Credit goes to [bobert](https://github.com/rstrand2357) for figuring out how to solve this.

duckythescientist

#!/usr/bin/env python2

"""
Angr would probably be the nice way to solve this. Oh well.
Brute force worked for me.

Trying different inputs, it seems the length doesn't matter.
The output changes depending on how many characters at the beginning match the key.
Brute force possible keys watching for output changes (to know when we got the right letter)

duckythescientist

#!/usr/bin/env python2

"""
The pcap is a capture of a USB keyboard. 
The proper way to tell is by finding the VID/PID combination during enumeration then looking up the device from that.
The easy way is just to have looked at enough USB stuffs to recognize that it's a keyboard. :)

The keyboard data exists in the USB Leftover section. `tshark` is our friend for extracting this.
tshark -r ./intercept.pcapng -T fields -e usb.capdata -Y usb.capdata 2>/dev/null
This has some trailing data that we don't care about it, so use tail to skip the beginning 6 lines.