A non perl solution but depending on the time to develop a solution might be worth the cost
<http://www.tethyssolutions.com/automation-software.htm> John Eisengrein, Peter wrote: > Dan had emailed me directly asking how he might go about doing a packet > capture, to which I replied directly. I thought it might be useful to others > on the list, so I'm sharing the wonder that is Wireshark (was Ethereal). > > -Pete > > -----Original Message----- > From: Eisengrein, Peter > Sent: Tuesday, December 12, 2006 7:40 AM > To: 'Dan Jablonsky' > Subject: RE: lazy, lazy, lazy > > > Download a copy of Wireshark www.wireshark.org -- it is an open source > sniffer. Run that on the same machine as the client app and you can capture > all data from that pc. You can also filter the capture or the results, which > will make it easier to see data between you and the server, assuming you know > the IP of the server. Wireshark is fairly intuitive after you've used it a > couple times and it allows you to drill down into each packet, seeing all the > headers and the raw data itself. > > -Pete > > > >> -----Original Message----- >> From: Dan Jablonsky [mailto:[EMAIL PROTECTED] >> Sent: Monday, December 11, 2006 5:41 PM >> To: Eisengrein, Peter >> Subject: RE: lazy, lazy, lazy >> >> >> Thanks Peter, >> I am preparing for the worst ... is there a place you >> can point where I could find more details on >> >>> perform various tasks with the client, >>> see what binary data is sent/received >> i'm not sure I know where to start ... >> Thanks a bunch, >> Dan >> >> --- "Eisengrein, Peter" <[EMAIL PROTECTED]> >> wrote: >> >>>> Now I'm left with a few maneuvers that use a >>>> client-server app, it is possible to automate >>> those in >>>> any way. Unfortunatelly I don't have any access to >>> any >>>> internals of those applications, only permissions >>> on >>>> the file system, network and all ... >>>> I would like to try only for the fun of it, if >>> anybody >>>> has any ideas, please let me know, >>>> Thanks, >>>> Dan >>>> >>> Without knowing anything about the apps, I'm >>> guessing best-bet would be to find out what command >>> line args it will accept and then use system(). Or, >>> if it doesn't do anything from command line, run the >>> actual client and snoop the communication to find >>> out what port(s) and protocol(s) it uses. And, if >>> you're lucky it will communicate in clear text. >>> Otherwise, you would have to perform various tasks >>> with the client, see what binary data is >>> sent/received, and experiment by sending data using >>> IO::Socket. If you have to do the latter, do it on a >>> development server if at all possible. >>> >>> Good luck. >>> >> >> >> >> ______________________________________________________________ >> ______________________ >> Do you Yahoo!? >> Everyone is raving about the all-new Yahoo! Mail beta. >> http://new.mail.yahoo.com >> > _______________________________________________ > Perl-Win32-Users mailing list > Perl-Win32-Users@listserv.ActiveState.com > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > > _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
