Hacker Moleskine

The one-line version: I expected a structured, symbolic memory to beat store-raw1 on counting, temporal, and conflict questions.

The problem: the agent starts every session as a stranger A coding agent is brilliant for an hour and then born again, blank, the next morning.

A byte signature is how a reverse engineer says "this function, the one I named and annotated last week, is the same code over here in the new build."

A while back I wrote about using Cython to speed up IDA Pro plugins: you keep the Python plugin ecosystem, you cross the Python/C boundary once, and you let the heavy loop run as C.

When you write shellcode by hand, you typically end up with something like this: const uint8_t shellcode[] = { 0x48, 0x89, 0xc3, // mov rbx, rax 0x48, 0x83, 0xc0, 0x10, // add rax, 0x10 0xc3 // ret }; It works, but it is error prone.

Python is an incredibly powerful language.

Sensitive data is valuable, but possessing it is risky and costly.

As we say goodbye to 2012 and welcome 2013, I'd like to reflect on the opportunities ahead, but first, I want to say a few words about last year.

Nose is a fantastic testing framework.

I had a need to trace a function's call stack to identify call chain paths in some difficult-to-follow Python code that was laced with lots of magic and abstractions.

I've recently had to do some work that required sorting a very large CSV file, containing fields with embedded newlines, quickly.

Over the weekend, I was working on upgrading python-ngrams because I had discovered a bug where the tokenization was incorrect.

I just recently purchased a MacBook Pro, which comes with Snow Leopard installed, and I noticed that it comes with python 2.6.1 installed.

At work, I'm migrating over python to our 64bit machines and one thing that I've noticed was that there really was no standard python 64bit verification method to ensure the build was really 64bit or not.