Reference: http://www.cnx-software.com/2012/07/31/84-mb-minimal-raspbian-armhf-image-for-raspberry-pi/
curl -O https://dl.dropbox.com/u/45842273/2012-07-15-wheezy-raspian-minimal.img.7z
yum install p7zip
7za e 2012-07-15-wheezy-raspian-minimal.img.7z
qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append "root=/dev/sda2 panic=1" -hda 2012-07-15-wheezy-raspian-minimal.img -net nic -net user -vnc :0 -net tap,ifname=vnet0,script=no,downscript=no
| STEP 1: Insert security key and cat /var/log/messages (or tail -f /var/log/messages and then insert security key) | |
| Although some recent versions of Linux have built-in support for U2F security keys, many do not, and you may therefore have to make a minor system configuration change in order to allow the requesting web browser (such as Chrome) to communicate directly with your Key-ID U2F token via the USB port. | |
| This is a system-wide configuration update that enables Key-ID U2F functionality on Linux for all users, and is entirely safe. It uses standard Linux udev rules, which allows you to identify and thus allow certain devices, based on their specific properties, such as its USB Vendor ID and Product ID. | |
| The Feitian FIDO U2F token has a Vendor ID (VID) of 096e (hex) and a Product ID (PID) of 0854 (hex). To enable it on Linux, assuming you are running udev version 188 or later, simply create the file /etc/udev/rules.d/70-u2f.rules with the following contents: | |
| # Builds NGINX from the QUIC+HTTP/3 development branch | |
| # - Based on the official NGINX docker image, including all modules built by default | |
| # - OpenSSL replaced with LibreSSL to support QUIC's TLS requirements (statically linked) | |
| # | |
| # docker build --no-cache -t nginx:quic . | |
| # docker run -d -p 443:443 -p 443:443/udp nginx:quic | |
| # | |
| # Note that a suitable configuration file and TLS certificates are required for testing! | |
| # See <https://quic.nginx.org/readme.html> for more info |
| base { | |
| // debug: connection progress & client list on SIGUSR1 | |
| log_debug = on; | |
| // info: start and end of client session | |
| log_info = on; | |
| /* possible `log' values are: | |
| * stderr | |
| * file:/path/to/file |
The included script 'widevine-flash_armhf.sh' fetches a ChromeOS image for ARM and extracts the Widevine and Flash binaries, saving them in a compressed archive. Since it downloads a fairly large file (2Gb+ on disk after download) it is recommended that you run the script on a raspberry that has plenty of disk space.
The files in the compressed archive are copied to the folder /usr/lib/chromium-browser/
To run the file just type the following:
sudo ./widevine-flash_armhf.sh
Check out this tutorial: https://lemariva.com/blog/2020/06/raspberry-pi-amazon-prime-netflix-and-drm-solution
| chain --autofree https://boot.netboot.xyz |
| (Note: tested on Ubuntu 19.10 host/x86_64 machine) | |
| ~~ | |
| Install dependencies: | |
| apt-get install binutils-aarch64-linux-gnu gcc-9-aarch64-linux-gnu bison flex build-essential kpartx | |
| sudo apt-get install libgmp-dev libmpfr-dev libmpc-dev | |
| cd /usr/bin | |
| sudo ln -s aarch64-linux-gnu-gcc-9 aarch64-linux-gnu-gcc | |
| # Build armstubs: |
| #!/bin/sh | |
| # https://crosp.net/blog/administration/routing-network-traffic-through-socks5-proxy-using-dd-wrt/ | |
| # https://serverfault.com/questions/200635/best-way-to-clear-all-iptables-rules | |
| PROXIFYING_MACHINE=192.168.82.192 | |
| MACHINE_TO_PROXIFY=192.168.83.0/24 | |
| NETWORK=192.168.83.0/24 | |
| WAN_IP=192.168.81.1 | |
| iptables -I PREROUTING 1 -t mangle -s $MACHINE_TO_PROXIFY ! -d $NETWORK -p tcp -m multiport --dports 80,443 -j MARK --set-mark 3 |
