This should make True Color (24-bit) and italics work in your tmux session and vim/neovim when using Alacritty (and should be compatible with any other terminal emulator, including Kitty).
Running this script should look the same in tmux as without.
curl -s https://gist.githubusercontent.com/lifepillar/09a44b8cf0f9397465614e622979107f/raw/24-bit-color.sh >24-bit-color.sh
| #!/usr/bin/env python3 | |
| import json | |
| import subprocess | |
| import argparse | |
| from xdg import BaseDirectory | |
| from pathlib import Path | |
| def get_output_current(): |
http://llvm.org/docs/ProgrammersManual.html#the-llvm-debug-macro-and-debug-option https://clang.llvm.org/docs/UsersManual.html#controlling-size-of-debug-information
-fno-discard-value-names
-g0
Don’t generate any debug info (default).
-gline-tables-only
by 0xabad1dea September 2018
You may notice a decidedly Nintendo bias to the examples. I can't change who I am.
Speedrunning is:
https://gbatemp.net/threads/nintendo-switch-sd-to-nsp-dumper.514816/ for a more automated and easier way to do this
This guide assumes you have previous experience with hactool and messing with your NAND. You aren't supposed to blindly copy commands in this, so read before pasting!
Also, the Python sections require Python 2.7 and pycrypto. Make sure your hactool is v1.2 or above.
| #!/usr/bin/env python3 | |
| import os | |
| """ | |
| Cursed Code. | |
| This code literally patches your kernel memory, proceed at your own risk. | |
| Tested on Ubuntu 17.10 and Arch, x86_64. Should work on other distros, maybe even other architectures! |
| Leaked Keys: | |
| ============ | |
| sha256(master_key_00) = 0EE359BE3C864BB0782E1D70A718A0342C551EED28C369754F9C4F691BECF7CA | |
| sha256(master_key_01) = 4FE707B7E4ABDAF727C894AAF13B1351BFE2AC90D875F73B2E20FA94B9CC661E | |
| sha256(master_key_02) = 79277C0237A2252EC3DFAC1F7C359C2B3D121E9DB15BB9AB4C2B4408D2F3AE09 | |
| sha256(master_key_03) = 4F36C565D13325F65EE134073C6A578FFCB0008E02D69400836844EAB7432754 | |
| sha256(package1_key_00) = 4543CD1B7CAD7EE0466A3DE2086A0EF923805DCEA6C741541CDDB14F54F97B40 | |
| sha256(package1_key_01) = 4A11DA019D26470C9B805F1721364830DC0096DD66EAC453B0D14455E5AF5CF8 | |
| sha256(package1_key_02) = CCA867360B3318246FBF0B8A86473176ED486DFE229772B941A02E84D50A3155 |
| { | |
| "version": { | |
| "format": 1, | |
| "semantics": 1 | |
| }, | |
| "news_id": 10000, | |
| "published_at": 0, | |
| "pickup_limit": 1209600, | |
| "priority": 50, | |
| "deletion_priority": 0, |
So you want to decrypt switch content ? Well, the good news is that all the tools required to do that are written up! The great news is, since this is crypto we're talking about, you'll have to find the keys. Yourself. Like it's easter.
So here you can find a template of the $HOME/.switch/prod.keys file that hactool uses to decrypt content. It contains all the SHA256 and location of the keys and seeds, so you can find them yourselves.
Note that all the seeds (the keys that end with _source) are used along with the master_key_## to derive an actual key.
If you have somehow obtained the key without the seed, you can rename xxx_source to xxx_## (where ## is the master key number) and put your key there.