4 ms·
> You can't block accessibility on the OTP app because then blind people will not be able to use it. You can block accessibility from the specific field of the
by derefr 7y ago
> You can't block accessibility on the OTP app because then blind people will not be able to use it.
You can block accessibility from the specific field of the OTP app, if you also have a system framework that retrieves exactly the contents of that field into your paste buffer when you interact with a privileged UI element (i.e. the keyboard-UI “autofill 2FA” accelerator.)
- insomniacity 7y agoWhat about people who want to type the code into a different device?
- tbrock 7y agoBut then how would disabled people access their 2fa codes?
- 1MachineElf 7y agoMaybe the app should just read the code out to the user, provided said user has a headset on.
- Klathmon 7y agoaccessibility services can also tap into the audio output of the device.
- ihuman 7y agoThat won't work if someone it trying to use the code on their desktop. The screen reader won't be able to read the code to them, so they won't be able to log in.
- derefr 7y agoYou can autofill the field into a text editor, and read it from there. The security comes from the fact that you had to interact with a privileged UI element to do so, which an accessibility assistant cannot trigger; you need to use the system accessibility features (e.g. the voice assistant) to trigger privileged UI elements. (See also: accessibility of elevation prompts in Windows.)
- zepto 7y agoThee is no reason not to have a special privilege level for screen readers.
- akerl_ 7y agoThere is a special privilege level for screen readers. The issue is that the hypothetical malicious app pretends to be a screen reader.
- zepto 7y agoDo you mean it hypothetically actually functions as a screen reader but also steals data, or something that just requests the privilege while being something completely different?
- akerl_ 7y agoEither one, but realistically the latter. In the former case, you just call your app SuperLegitScreenReader, prompt the user to grant accessibility access, and then snarf up data. Bonus points if you bundle in some open source or pirated screen reader code so your app can act the part, but you could probably just say “fetching reader data, screen reading will be functional in ~60 minutes” and count on most users to not bother uninstalling the app or revoking permissions. In the latter case, you call your app “CandyNinjaBirds”, and have it pop up and say “to let you share cute stickers to your friends, you need to enable accessibility access” and count on the vast majority of people to click “allow”. The latter case is way more common because the former case limits your target audience to people who actually want a screen reader.
- zepto 7y agoOk - but given the small number of actual screen readers it would be easy for a store to have extra policing for this privilege.
- Anon1096 7y agoThe copy/paste buffer is also accessible via accessibility features. This isn't a fix for the "problem" presented by the article. (personally I think it is hardly an issue)