TL;DR This approach requires you to be on a non-RISC-V Arch Linux (x86_64 or aarch64, etc.) machine, because we use pacstrap and pacman . 1 2 3 4 5 6 7 # pacman -Syu then reboot is recommended before this sudo pacman -S arch-install-scripts git qemu-img qemu-system-riscv riscv64-linux-gnu-gcc git clone https://github.com/CoelacanthusHex/archriscv-scriptlet.git cd archriscv-scriptlet ./mkrootfs ./mkimg …
XieJiSS, revision 3 This article may not be updated in time, please refer to the RV64 board replacement rootfs guide – archriscv-packages Wiki 0x00 warning Make sure you or your partner have physical (via serial) access to the board. Otherwise, your board will lose connection at step 6 at 0x02 reboot. 0x01 Preparations First, go …
safer-telegram-bot-1 Search for flag1 in the source code 1 const user1 = createUser(~~( 1 + Math .random() * 1000000 ), “test” , fs.readFileSync(__dirname + “/flag1.txt” , “utf8” )); Search for user1.flag 1 2 3 4 5 6 7 8 9 10 11 12 13 bot.on( “callback_query” , async (query) => { const callbackData = query.data …