Use an older USB 2.0 stick, newer ones will most certainly not work.
sudo dd if=debian-11.0.0-powerpc-NETINST-1.iso of=/dev/sda1 status=progress # Or use GNOME Disks, Etcher etc.
sync| /dts-v1/; | |
| / { | |
| #address-cells = <0x01>; | |
| #size-cells = <0x01>; | |
| model = "Qualcomm Technologies, Inc. IPQ40xx/AP-DK04.1-C1"; | |
| compatible = "qcom,ipq40xx-apdk04.1\0qcom,ipq40xx"; | |
| interrupt-parent = <0x01>; | |
| qcom,board-id = <0x08 0x00>; | |
| qcom,msm-id = <0x111 0x00>; |
In Adobe Flash Player versions newer than 32.0.0.344 they added a "Timebomb" for the EOL.
the player would refuse to run any custom flash content after 12/01/2021,
instead it would just show this
So knowing this, Lets crack it!
I acturally started looking into this before the 12/01/2021 hit, but only recently did i acturally discover a way to bypass the killswitch
(also- im aware this is not the only way to do this, i might not have been first, but i still did do it)
well, only a matter of time before Chrome turns off pepper plugins at all, but let's have fun while we can
flash player keeps a floating point timestamp of the time when flash should stop working, it can be patched to Infinity (thanks, floats!) and flash should keep working forever
on my version (straight from arch repos, md5sum b6da1630859c4f9c47c8ac26ec9c57a3) the timebomb timestamp is at offset 00EB7760, you need to change 00 00 40 46 3E 6F 77 42 to 00 00 00 00 00 00 F8 7F. here's a script to automate that, it also makes a backup
in case the timestamp isnt there, or you have a different md5 hash, you can just search for the timestamp with any hex editor
| # Enable "charge + tether" in Settings -> Setup -> Mobile Router Setup -> Tethering | |
| # Use a usb cable to connect (tethering) to the router on port 5510 | |
| # Useful links: | |
| # Verify the IMEI number | |
| # https://en.wikipedia.org/wiki/Luhn_algorithm | |
| # Challenge/Response Generator for Sierra Wireless Cards V1.0 | |
| # https://github.com/bkerler/SierraWirelessGen | |
| ATI |
| # All possible descrypt hashes of the password 'admin', using all possible salts. | |
| # From https://github.com/roycewilliams/kens-salty-rainbow | |
| # If you find a device that always uses one of these, let me know. | |
| ..xpoEyRReGzk | |
| ./nlIXYriZaB2 | |
| .08iPeaCLti3E | |
| .1fH80ykoJAyI | |
| .23PstrXfk7Nw | |
| .37vRhjo4ZP66 | |
| .4nTonCOGSWyU |
The purpose of this document is to get you familiar with the concepts and command line tools involved with connecting to the internet using modern 4G LTE modems on both Debian/Ubuntu and OpenWRT.
This writeup is based on my experiences with the Sierra Wireless AirPrime MC7455 modem and a Calyx (Sprint) SIM card, but it should apply to most modern 4G LTE modems.
These are the steps required:
| #!/bin/bash | |
| if [ ! -d files ]; then | |
| # Make the content | |
| echo "Generating root content.." | |
| mkdir files | |
| echo "$(date)" > files/date.txt | |
| echo "Another content" > files/other.txt | |
| fi | |
| #These config are based by Nand device that you will use! |
I’m currently working (I’m just at the beginning, and I’m quite slow) on a personal project that will use Keepass files (kdb and kdbx).
I tried to find some documentation about .kdb and .kdbx format, but I didn’t find anything, even in the Keepass official website. I you want to know how these file formats are structured, you must read Keepass’s source code. So I wrote this article that explains how Keepass file format are structured, maybe it will help someone.