Skip to content

Instantly share code, notes, and snippets.

#!/bin/sh
security find-generic-password -a "$1" -g 2>&1 | grep password | sed -e "s/password: \"//" -e "s/\"//"
@aussiehash
aussiehash / Dockerfile
Last active August 29, 2015 14:27 — forked from andychase/Dockerfile
Faking XT Nodes for fun
# Use the Ubuntu Linux distro as the base for this image
FROM ubuntu
# Install necessary build tools
RUN apt-get update && apt-get upgrade --yes && apt-get install build-essential clang git --yes
# Download and install PseudoNode
RUN cd /root && git clone https://github.com/basil00/PseudoNode.git && cd ./PseudoNode && make
# These two commands enable port 8333 to be routed and start the node by default
EXPOSE 8333
CMD ["bash", "-c", "cd /root/PseudoNode && ./pseudonode --stealth --coin=bitcoin-xt"]
@aussiehash
aussiehash / obsetup.sh
Created May 8, 2016 19:58 — forked from mariodian/obsetup.sh
OpenBazaar Server installation script for Ubuntu
#!/bin/bash
# Run: "chmod u+x obsetup.sh" before running the script
user=$(whoami)
dir=$(pwd)
if [ $user = 'root' ]; then
echo "Please run this script as a regular user."
exit;
fi
@aussiehash
aussiehash / htc_vive_watchman_codes
Created December 10, 2016 22:04 — forked from cnlohr/htc_vive_watchman_codes
HTC Vive Watchman Hacking Codes!
So, the way this goes is I post my AVR code, then I post what the HTC Vive does.
The output is: POST 0: (# of bytes) (IMU Timecode MSBs) (All raw light data)
(All raw light data ends with [3 bytes, LSB timecode] [OTA CRC (probably ignore)])
Events (TIME): (LED CODE 1)/(TIME CODE 1/TIMECODE 2)/(LED CODE 2)/(TIME CODE 3/TIMECODE 4)...
//NOTICE: The funky encoding of the numbers, and the fact that paramters are read from the end of the data going forward.
//We know we're done when the # of parameters read is (# of bytes left*2)-1
@aussiehash
aussiehash / trezor_one_fw_upgrade.cmd
Created February 28, 2019 01:56 — forked from brianddk/trezor_one_fw_upgrade.cmd
Windows batch trezor FW upgrade
@echo off
rem choco install -y openssl.light
rem choco install -y wget
rem choco install -y cygwin
rem tail -c +257 trezor.signed.bin | sha256sum
rem https://crt.sh/?q=26AFA022ADC5EE7E41A5226C1DE336D438F1AD0F
setlocal
set tail=%ChocolateyToolsLocation%\cygwin\bin\tail.exe
set sha256sum=%ChocolateyToolsLocation%\cygwin\bin\sha256sum.exe
set openssl="%ProgramFiles%\OpenSSL\bin\openssl.exe"
@aussiehash
aussiehash / satoshistreasure.md
Created April 17, 2019 02:22 — forked from johncantrell97/satoshistreasure.md
How I Obtained Satoshi's Treasure Keys 1, 2, and 3 in Minutes

Today (April 16th 2019 at noon) the first major clues to discover key #1 was set to be released in a few cities. A QR code with the words 'orbital' were found at these locations and looked like this: (https://imgur.com/a/6rNmz7T). If you read the QR code with your phone you will be directed to this url: https://satoshistreasure.xyz/k1

At this URL you are prompted to input a passphrase to decrypt the first shard. An obvious first guess was to try the word 'orbital' from the QR code. Not suprisingly this worked! This reveals a congratulations page and presents the first key shard:

ST-0001-a36e904f9431ff6b18079881a20af2b3403b86b4a6bace5f3a6a47e945b95cce937c415bedaad6c86bb86b59f0b1d137442537a8.

Now, we were supposed to wait until April 17th to get clues from the other cities for keys #2 and #3 but that wouldn't stop me from digging around with all the new information we had. All that time "playing" notpron (http://notpron.org/notpron/) years ago was going to help me here.

The first thing I noticed was

## Getting LND working with Dojo
## Start Dojo
$ cd /path/to/docker/my-dojo/ && sudo ./dojo.sh start
## Login to the bitcoind docker container as root
$ sudo docker exec -u root -it bitcoind /bin/bash
## Update and install a text editor
$ apt-get update && apt-get install nano
All credit goes to Mark Engelberg (https://github.com/Engelberg) for figuring this out!
His original writeup can be found at:
https://gist.github.com/Engelberg/aac9da2f27b723683982d187bd4d5ea4
Thought I'd just write more of a follow along tutorial for the less technical
## Written for use with Ubuntu Desktop 18.04 LTS ##
## Stop your Dojo
###### User friendly interface script for interaction with ./dojo [command] ######
## Written for use with Ubuntu Desktop 18.04 LTS ##
This script is setup to run locally from the machin that your Dojo is installed on, but if you wanted to use it via SSH
there is a write up below the script on how to set that up.
## Open a terminal
$ mkdir scripts
$ cd scripts && touch control_dojo.sh