
- QNAP QBLOCKER PASSWORD
- QNAP QBLOCKER DOWNLOAD
I was able to stop the process, thankfully. I'm probably a lucky SOB and don't deserve this.
Not easy to remember everything next to work and kids. But maybe this was during Wednesday and too late, I can't remember it exactly anymore. I was not on the latest firmaware, but I did recently "harden" the system with the Counselor. I've now shutdown the NAS completely, pondering my next move and also planing for the future to avoid having this again.
QNAP QBLOCKER DOWNLOAD
had to download 7zip via homebrew, decryption worked!.
QNAP QBLOCKER PASSWORD
first decrypting via my OSX native zip did not accept the password so I thought this didn't work. seconds after that I got the password in the logfile: yugiohnl you're an unsung hero!. I basically followed the above linked guide but realized in my case the local 7 zip doing the work was named `7z.orig` and thus I had to adapt the file names. my best guess, based on the readme timestamp, is that it all started this Wednesday but due to the sheer number of files on the one share, it was still working on it. which in my case made me lucky because the "stuff from last century" is less important than what I had on the other shares following. I now assume it's going through the shares alphabetically, first placing the README and then starting to encrypt stuff. I've more shares, alphabetically following the first two, which are yet untouched. But the number of files, big and small, is extremely high and this is the share were the encryption was still running
the second one was my "archive from the last century" stuff, even I don't know anymore what there is.
the first one was completely encrypted but only had like 3 files or so. I've multiple shares but only two were encrypted. I then followed the procedure and extracted the password successfully and confirmed it with a few samples, but until I've everything back it's not time to party yet. This motivated me to regain hope and I enabled remote terminal access and logged in, and lo' and behold I found multiple 7z related processes STILL BEING ACTIVE. The encryption key would be stored in /mnt/HDA_ROOT/7z.log which you can then use to decrypt Cd /usr/local/sbin printf '#!/bin/sh \necho 60000' > 7z.sh chmod +x 7z.sh mv 7z 7z.bak mv 7z.sh 7z