JakeGinesin

/* author: jake ginesin */
/* i am not liable for the usage of this code. it is provided for demonstrational purposes 
  * :thumbs_up: */

(() => {
  /* params */
  const THREADS      = navigator.hardwareConcurrency || 4; // logical cores
  const RANDOM_BYTES = 256;                                // size of fake image
  const PAYLOAD      = 'IFA_PAYLOAD_TEXT';                 // hard-coded text (UNUSED FOR NOW)
  const BATCH        = 64;                                 // blobs / DB write

JakeGinesin

/* author: jake ginesin */
/* i am not liable for the usage of this code. it is provided for demonstrational purposes 
  * :thumbs_up */

(() => {
  /* params */
  const THREADS      = navigator.hardwareConcurrency || 4; // logical cores
  const RANDOM_BYTES = 256;                                // size of fake image
  const PAYLOAD      = 'IFA_PAYLOAD_TEXT';                 // hard-coded text (UNUSED FOR NOW)
  const BATCH        = 64;                                 // blobs / DB write

JakeGinesin

Simple infrastructure for creating an analysis environment for lksctp.

Installation and Setup

First, you'll need the lksctp package for your OS, which you can find at https://github.com/sctp/lksctp-tools. For arch linux, I used https://archlinux.org/packages/community/x86_64/lksctp-tools/

We use the loopback network interface lo, though we could hypothetically dockerize this setup if need be.

On our localhost, we need to set a delay so the attacker can actually inject the packet in the right place. To do so, use:

JakeGinesin

Keybase proof

I hereby claim:

• I am JakeGinesin on github.
• I am jake_g (https://keybase.io/jake_g) on keybase.
• I have a public key whose fingerprint is 3AF2 53AF 100D 4724 EB77 603A 2AB0 3833 F8E6 971C

To claim this, I am signing this object: