Title: Simple Sabotage Field Manual Author: Strategic Services Office of Strategic Services
| # These are my notes, circa Jan 17, 2017 for full volume encryption using customer supplied encryption keys (CSEK) | |
| # Caveat emptor. | |
| # Install Google Cloud Platform (GCP) SDK command line tools | |
| curl -s -L -O -J https://sdk.cloud.google.com/ | |
| # (inspect and run it) | |
| # Cloud KMS/keyring not needed for one-off volume encryption with CSEKs | |
| # gcloud beta kms keyrings create KEYRING_NAME --location LOCATION |
Short version: I strongly do not recommend using any of these providers. You are, of course, free to use whatever you like. My TL;DR advice: Roll your own and use Algo or Streisand. For messaging & voice, use Signal. For increased anonymity, use Tor for desktop (though recognize that doing so may actually put you at greater risk), and Onion Browser for mobile.
This mini-rant came on the heels of an interesting twitter discussion: https://twitter.com/kennwhite/status/591074055018582016
| #!/usr/bin/env bash | |
| # | |
| # Download tar file for "tree" here: https://oldmanprogrammer.net/source.php?dir=projects/tree | |
| # Maintained here: https://github.com/Old-Man-Programmer/tree | |
| # (No, really. It's 10+ years old, and updated as recently as Nov 25, 2024) | |
| # | |
| # I think this requires XCode pre-installed for gcc etc. | |
| curl -LO https://github.com/Old-Man-Programmer/tree/archive/refs/heads/master.zip | |
| unzip ./master.zip |
| package main | |
| import ( | |
| "crypto/tls" | |
| "golang.org/x/crypto/acme/autocert" | |
| "log" | |
| "net" | |
| "net/http" | |
| ) |
Vijaya Selvaraju North Indian Chicken Korma (https://www.youtube.com/watch?v=935VEghEnio)
INGREDIENTS
5 tbsp, Canola Oil
2 medium Onions, chopped
10 raw Cashews
1 cup, Whole Yogurt
1/2 tsp, Turmeric
This is the setup that worked for me after half a day of hacking around and chasing rabbit holes down old forum posts and open & closed Github issues.
Problem: While Go integration with VS Code is pretty slick in general, I needed to
pass compile-time build flags, e.g., -tags foo[^1] to go build and go run
directives, and I wanted to be able to properly debug with breakpoints etc. While there
are some promising tutorials out there like this on Digital Ocean and on Log Rocket it turned
out that one of the first things they both say to do is add the Delve extension to VS Code,
To override Big Sur's Gatekeeper restriction: "cannot be opened because the developer cannot be verified" from the command line
Example with MongoDB (can be run against a folder e.g., JavaSDK or individual executables):
xattr -d com.apple.quarantine /Users/me/Downloads/mongodb-macos-x86_64-enterprise-4.4.2/bin/*
This appears to be sticky for all identical versions of that executable, i.e., if you have two copies of the identical binary in unrelated directories, removing quarantine for one seems to enter a file signature hash into the allowed list globally.
I'm well aware of how old the version of Bash is that ships with MacOS and Apple's public deprecation plans. That said, I don't like having to fiddle with this in VS Code and every other tool that tries to be clever. This will kill the message everywhere for processes of this user. Don't bother screwing around with $HOME .bashrc .profiile .bash_profile BS. Or do, but realize the local config specific to the user won't suffice for VS Code et al. You can also use Brew to do this, which will use the most recent version of Bash, but I have a love-hate relationship with Brew and prefer to use this approach instead. Caveat Emptor: This works for me, but use at your own risk.