Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 Jul 2011 03:07:29 -0500
From: "JimF" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: Re: Johnny GUI interactive status from John

Still trivial.  Within john, create a new command arg, -winmsg or something. 
This could be a non-documented (i.e. does not show on the 'help' screen), 
and should only get built into john in a windows build.

When john processes that command (only valid for windows), john simply 
creates a hidden window, spawns a thread that is a 'winproc' thread. That 
thread will easily be able to pump messages.   This can be used just like 
the code which monitors tty keystrokes.  I believe that code simply sets a 
global.  Then at certain points, john checks that global, and when set, 
outputs a line of text.

So, johnny starts john, with a new command arg, john then sets up a windows 
message pump, and the 2 processes can chat with each other all they want. 
Trivial winblows 101 programming.

A 'registered' message is simply a way that 2 processes can get a specific 
unique message number, without having to be built knowing information about 
the other. It does not have to be coded that way at all.  Both processes, if 
built 'together', can simply choose to use the same number (a message is 
nothing more than a number).

Jim.

----- Original Message ----- 
From: "Shinnok" <admin@...nnok.com>

Windows messages are of two types: window messages and thread
messages(PostThreadMessage) for headless applications.
Both messaging routines require a message queue(for WM_USER++) and
thus a loop to be run that checks for incoming ones, which seems
unlikely for JtR.
http://msdn.microsoft.com/en-us/library/ms644927(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/ms644946%28VS.85%29.aspx

Even if we'd like to do it somehow and would create a message
marshaling thread for John, we still couldn't find out which of the
two John threads to send the message to:
http://stackoverflow.com/questions/3083903/postthreadmessage-to-another-process


Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ