set disassemble-next-line on
set dissasembly-flavor intel
b _start
run
while 1
#!/usr/bin/env bash | |
git branch -r | grep -v '\->' | while read remote; do git branch --track "${remote#origin/}" "$remote"; done | |
git fetch --all | |
git pull --all |
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.
@ECHO OFF | |
TITLE CertNXtractionPack by SocraticBliss and SimonMKWii (R) | |
ECHO: && ECHO PRE-REQUISITES: | |
ECHO -- Get your BIS Keys (via biskeydump) | |
ECHO -- Dump your SYSNAND (via hekate) | |
ECHO -- Decrypt your PRODINFO (BIS 0 Key) and Save to file - PRODINFO.bin to your working directory (via HacDiskMount) | |
ECHO -- keys.txt (ie. key = 32 digit hex value) file with the following keys... | |
ECHO --- master_key_00 | |
ECHO --- rsa_private_kek_generation_source |
############################################### | |
# TX SX OS unpacker - by hexkyz and naehrwert # | |
############################################### | |
from Crypto.Cipher import AES | |
from Crypto.Util import Counter | |
import os | |
import struct | |
""" |
# The following is adapted from https://github.com/reswitched/loaders/blob/master/nxo64.py | |
# | |
# =========================================================================================== | |
# | |
# Copyright 2017 Reswitched Team | |
# | |
# Permission to use, copy, modify, and/or distribute this software for any purpose with or | |
# without fee is hereby granted, provided that the above copyright notice and this permission | |
# notice appear in all copies. | |
# |
scenario: you have a windows vm failing to boot with INACCESSIBLE_BOOT_DEVICE
and changing the
disk type to ide or something else causes another bsod. how to you get it to boot up again without
a physical machine?
download the stable virtio drivers from here, in iso form: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
add the iso to your qemu/virt manager config as a cd/dvd drive
windows should send you to the recovery mode screen, but if it doesn't you might have to run a windows install iso to get to it.