![]() |
Re: nothing is safe ....
Quote:
|
Re: nothing is safe ....
Quote:
Initial cursor position, but that's controlled once the user has made a move long enough to bump one edge of the screen. Screen resolution, as mentioned, matters, but in practice can be reduced to a short list instead of all possible dimensions. I guess acceleration could mess things up, if you use it, but odds are trying various minimum and maximum settings from different desktops would get it. So you've got absolute positions of all clicks. (How to know when you've got these accurate? Analyze patterns; for example, the Windows taskbar is normally at the bottom of the screen, and you should see some activity there if you've got the height right. Compare ones that bounced off the bottom limit to ones coming directly from the top limit; they should match up. In general, look for clustered clicks coming from the top, and corresponding clusters from the bottom, and similarly left and right.) Now to convert the click-list to keypresses, the entire code of the OSK in use is involved, but given only a handful of these in common use, you can assume they have that, and just need to guess which one is running. Location on-screen, and (if configurable) key pitch? You can estimate these from a bunch of click data, and the results will help confirm the OSK & layout; frequency analysis of the proposed keys will allow you to distinguish geometrically similar layouts (e.g. QWERTY vs. Dvorak). Now you should be able to translate large periods of of the click-list into text, some of which should be identifiable natural language; at this point, you know you've got everything right; start looking for passwords or whatever sensitive info was desired. |
Re: nothing is safe ....
Benson,
Thanks for the explanation! |
| All times are GMT. The time now is 02:45. |
vBulletin® Version 3.8.8