vantezzen

<?php
// Encrypt a string using a public key
// $string: String to encrypt
// $key: Public key block to use when encrypting
// return: encrypted, enarmored PGP MESSAGE block
function encrypt($string, $key) {
    $key = OpenPGP_Message::parse(OpenPGP::unarmor($key, "PGP PUBLIC KEY BLOCK"));
    $data = new OpenPGP_LiteralDataPacket($string, array('format' => 'u', 'filename' => 'stuff.txt'));
    $encrypted = OpenPGP_Crypt_Symmetric::encrypt($key, new OpenPGP_Message(array($data)));
    $enc = OpenPGP::enarmor($encrypted->to_bytes(), "PGP MESSAGE");

vantezzen

/**
 * Porkbun.com: Search domain names under certain price
 * 
 * by vantezzen (https://github.com/vantezzen)
 * 
 * Instructions:
 * 1. Go to https://porkbun.com/products/domains
 * 2. Open JavaScript Console
 * 3. Copy and paste this code into the console
 * 4. Before executing, customize the `config` object to your needs

vantezzen

/**
 * Porkbun search filter
 *
 * by vantezzen(https://github.com/vantezzen)
 *
 * Instructions:
 * 1. Go to https://porkbun.com/checkout/search?q=[ Name ]&all=1 - replacing "[ Name ]" with the name you want for your domain
 * 2. Open JavaScript Console
 * 3. Copy and paste this code into the console
 * 4. Before executing, customize the `filterConfig` object to your needs

vantezzen

Keybase proof

I hereby claim:

• I am vantezzen on github.
• I am vantezzen (https://keybase.io/vantezzen) on keybase.
• I have a public key whose fingerprint is F4E8 EF80 29D2 86C4 5319 68C0 448B 52C0 B742 3E90

To claim this, I am signing this object:

vantezzen

/**
 * easy-vm sandbox escape
 */
const EasyVM = require("easy-vm")

// Create our new VM we want to exploit
const vm = new EasyVM({
  // We specifically don't allow our VM to use the console
  console: false,
  timeout: 6000,

vantezzen

# This Docker Compose configuration can be used to set up a vaultwarden
# setup on the *local* network.
#
# Many existing configurations are meant to be used on a public network
# with a Let's Encrypt certificate, its own domain etc.
# This configuration is meant to remain in the local network and not get
# exposed to the public facing internet to provide an additional layer
# of security. This way, passwords will only sync when in the local network.
#
# This configuration assumes that it will be available from https://nasty.local:86