Do you think TSA/CBP is going to check the flash data lines to see if the MCU is scanning the flash internally?
This isn’t a standard USB flash controller… You would need to break the casing and physically probe it to figure out that something was off as far as I can tell. It’s not like the MCU broadcasts that it is scanning to the USB port.
If I got it right, you could easily detect this drive by just creating password.txt. as the article says it creation is intercepted and skipped. Hence if there is no password.txt afterwards, you know what you’re dealing with.
Still, you have to know this AND care.
It looks for a string “password:xyz” bring written to any file, where xyz is the password. If you get the password wrong it’ll just write the file normally
Do you think TSA/CBP is going to check the flash data lines to see if the MCU is scanning the flash internally?
This isn’t a standard USB flash controller… You would need to break the casing and physically probe it to figure out that something was off as far as I can tell. It’s not like the MCU broadcasts that it is scanning to the USB port.
If I got it right, you could easily detect this drive by just creating password.txt. as the article says it creation is intercepted and skipped. Hence if there is no password.txt afterwards, you know what you’re dealing with. Still, you have to know this AND care.
It looks for a string “password:xyz” bring written to any file, where xyz is the password. If you get the password wrong it’ll just write the file normally
Ah okay, so then I retract my statement and better my reading-skills 😁
It’s only skipping if your password matches. Otherwise it’ll just be a normal file.
Ah okay, so then I retract my statement and better my reading-skills 😁