You don't need to be so secretive. You can at least tell us what type of
hook you are trying to use; I think you have not even specified that. There
is probably more you can tell us. The type of hook might be very relevant;
for example, many hooks depend on a message loop and most console
applications do not have a message loop.
In the past, I have been told that hooks are a UI thing and are off-topic
for this newsgroup. You have cross-posted to many newsgroups that a hook are
not on-topic for.
As for "public consumption", I think you are saying too much by telling us
your company name and such. There is no need to divulge that, unless you
feel a need to convince us that your requirements are valid.
If, you truly are trying to make an application more secure, then there are
probably some more secure solutions. Of course, I could be wrong, especially
since there is such a minimal description of your requirements.
If I try to use Spy++ to analyze a console windoe, it says "The specified
window cannot be spied upon. Windows will not allow access to the message
stream for this window.". So there is something special about console
windows.
Post by Bob BinnsAh, the question arises? What indeed. If this is info not for public
consumption, then maybe private email would be better.
I am working for a security company (Sentillion) and we a locking down
and automating the login and patient selection for health care
applications. I have existing code base that works well with many
terminal emulators; I'm trying to adapt it to console apps.
Regards,
Bob
Post by SkywingWell, first, what are you trying to accomplish by hooking the console
window?
Post by Bob BinnsGood answer. But how do I do I set these privileges and what privileges
are they? Shall I use one on my incidents and call MS?
Thanks,
Bob
Post by SkywingThis is because CSRSS.exe owns those windows. You can't hook them
without special privileges.
Post by Bob BinnsI have a general Hook dll that loads into processes with Windows.
Works well with windows programs except on Console Applications like
cmd.exe and telnet.exe. I have tried a few variabtions of the hook.
I alsotried SetWinEventHook which works only sometimes. The Active
Accessibility event viewer works all the time.
With these calls, the call returns a success but my dll is never
loaded into the console process address space.
When I try to look at messages from the console window using Spy++, it
tells me the os has denied access.
Any Clues on how to hook these console processes?
Thanks,
Bob