-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB-C behavior & potential bypasses #579
Comments
Hi @pdolinic, maybe its just me but I think a few pictures and/or shell output would help to better understand the blocked-and-not-blocked situation that you're describing. Could you demonstrate for a particular device what parts of the system show that's blocked in detail and what parts don't? E.g. I'm unsure if we're talking a mounted file system here or more existence of a |
Hey @hartwork , thanks for replying So I've tested State:
Thanks |
could it be you do see the device show up but you cannot browse the filesystem(s) ? |
Even though USB-C connected devices show as blocked
usbguard list-devices
, they appear visible on the Linux file-system tree (thunar for example), (try it via a phone USB-C -> USB-C)Some investigation might be worth there, and if one could exploit simply adding USB-C Dongles on top of USB-A/USB-B.
The first time I found this interesting, was when playing around with USB-C Yubikeys.
The text was updated successfully, but these errors were encountered: