wxPython clipboard

[lbolognini]

Hi all,

I'm thinking about coding a free version of this software:
http://www.pitrinec.com/pkindex.htm

I would use wxPython and wx.Clipboard class (hoping to be able to make
it cross-platform)

The software above detects macros you code in any Windows active window
and replaces them with a text: something like you write "/ff" and he
pastes "Feel free to call us back for whatever questions you might
have".

This kind of softwares are very usefull in a call-centre environment
(where I'm currently working).

The thing is I'm thinking about the best approach (in terms of CPU
resources) to detect the macro. Not sure how keyloggers work but I
suspect I could run a service that compares everything beign written in
the active window with the macros I saved in the software
configuration.

Could you please give me some advice on the best approach to solve this
problem?

Thanks a lot,
Lorenzo

 

[Jeremy Bowers]

Could you please give me some advice on the best approach to solve this
problem?

To the best of my knowledge, and I'd be surprised if this wasn't true,
wxPython does not have the necessary tools to do this.

That program doesn't even use the clipboard; it uses low-level security
flaws* in Windows to directly access text in other programs as it is being
typed, watch for trigger text to go by, and then dynamically replace it;
all of which is a major security flaw in the absence of user permission.

This *particular* application is harmless, but it's still exploiting holes.

Since those holes don't exist cross-platform, wxWindows won't reflect
them. You'd need to go to the WinAPI, and after that I have no idea what
comes next... but I do know it's going to be tricky, painful work and if
you didn't already know you needed to do this, you probably don't want to
go here. Here There Be Dragons.

*: The security flaw lies in the Windows messaging model; once you have a
window handle you can send it any message and get back any data you want,
including stuffing that window with any new data you want, which is a
gaping flaw indeed in a world of buffer exploits. IIRC, there is no way to
do any sort of user-based security, so even if you do everything as a
low-priv user except use this one program as administrator, if that
program has a window on the screen and a buffer overflow, that's a root
exploit waiting to be coded.