x0nu11byt3

ELF Format Cheatsheet

Introduction

Executable and Linkable Format (ELF), is the default binary format on Linux-based systems.

Compilation

ZipFile

Retrieving Auth Token

1. Run the command:

   python pixiv_auth.py login

   This will open the browser with Pixiv login page.

aojea

ARG IMAGE=kindest/node
ARG VERSION=1.19
ARG MINOR=1
ARG OS=xUbuntu_20.04

FROM ${IMAGE}:v${VERSION}.${MINOR}

ARG VERSION
ARG OS

darfink

#!/usr/bin/python2
import argparse
import sys
import subprocess
from itertools import takewhile
from macholib import MachO, ptypes

def parse_rwx(text):
    return ('r' in text and 1) | ('w' in text and 2) | ('x' in text and 4)

vkobel

#include <linux/module.h>
#include <crypto/hash.h>

struct sdesc {
    struct shash_desc shash;
    char ctx[];
};

static struct sdesc *init_sdesc(struct crypto_shash *alg)
{

mrunkel

ZFS commands cheatsheet

Devices and Pools

List all devices in the server

lsblk -S

List all pools

zpool list

Russtopia

// Simple demo of a GO CGI program that takes
// file uploads.
//
// NOTE NOTE DANGER DANGER
// Absolutely No filename/path sanitizing is done,
// don't run this in production unless you want hackers
// to overwrite your server. This is only a demo of
// how to untangle the go stdlib form-related datatypes
// and use them to take file uploads.
//

notpushkin

?: your client unchoked the peer but the peer is not interested
D: currently downloading from the peer (interested and not choked)
d: your client wants to download, but peer doesn't want to send (interested and choked)
E: peer is using Protocol Encryption (all traffic)
e: peer is using Protocol Encryption (handshake)
F: peer was involved in a hashfailed piece (not necessarily a bad peer, just involved)
H: peer was obtained through DHT
h: peer connection established via UDP hole-punching
I: peer established an incoming connection
K: peer unchoked your client, but your client is not interested

coin8086

Use Proxy for Git/GitHub

Generally, the Git proxy configuration depends on the Git Server Protocol you use. And there're two common protocols: SSH and HTTP/HTTPS. Both require a proxy setup already. In the following, I assume a SOCKS5 proxy set up on localhost:1080. But it can also be a HTTP proxy. I'll talk about how to set up a SOCKS5 proxy later.

SSH Protocol

When you do git clone ssh://[user@]server/project.git or git clone [user@]server:project.git, you're using the SSH protocol. You need to configurate your SSH client to use a proxy. Add the following to your SSH config file, say ~/.ssh/config:

ProxyCommand nc -x localhost:1080 %h %p

hothero

package main

import (
	"bytes"
	"crypto/aes"
	"crypto/cipher"
	"encoding/base64"
	"fmt"
)