|
Well its for financial trading software. We have a free client but a financially secure protocol. Getting the keys out of the executable doesn't infringe on anyone's privacy, but it would enable us to do things at the protocol level directly. Unfortunately the trading client automation is event driven only, and I want to do things outside of the event model. We also have a problem because sleep() is severely broken, and the recent versions of the client say that if any client sleeps too much, it is considered hung and crashes it :/ I just want to read/write the protocol in a session I already have credentials for, but that requires reading the keys out of the exe, stored in some packed data region. I've been somewhat public about the idea and people are interested and supportive (emotionally and morally but not financially) but nobody I know has the skill to do packed disassembly reading. I identified 6 different data regions, I only need the crypto keys and I don't care about the rest or modifying the client in any way.
|