Repository navigation
>>> Try our new web flasher <<<
Fixed Issues
- Previously the drive would leave remnants of the file use for unlocking, this is not a security issue but more of an annoyance. Since the password was being wiped, the file would often be corrupted.
- It was annoying for people to format the first partition to FAT32 on the first useage.
What's Changed
The firmware will now...
- Create a FAT32 filesystem in the first sector if there isn't already a FAT32 filesystem.
- Still snoop for the password, matching against "password:xyz", just like before.
- Blank out this password, allow the file to be written to the disk, note the password length, offset and lba.
- Using
pending_pw_lba,pending_pw_offsetandpassword_lenfind the file and delete it. - Unlock the drive.
Notes on the Firmware
The 600k build provides greater resistance to offline password guessing but takes longer to unlock on the CH569 (3 mins). The 100k build unlocks faster (30 seconds), but requires only one-sixth as much work per password guess and is below OWASP’s current recommendation.
Choose based on the security/performance trade-off appropriate for your use case. Personally I used 100k with a good password.