Get into the server and execute perl command

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Get into the server and execute perl command by Corion (Patriarch) on Feb 24, 2015 at 20:29 UTC
The easiest way is to set up ssh port forwarding and run something like `ssh -L 3456:localhost:5678 that.other.machine` [download] Then, your local port machineA:3456 will be connected to the (localhost) port 5678 on machineB, and you can just use LWP::Simple to fetch `http://localhost_3456` and get data from `http://localhost:5678` on machineB.	[reply] [d/l] [select]
Re^2: Get into the server and execute perl command by Anonymous Monk on Feb 25, 2015 at 06:07 UTC
ok, suppose, I get into the server, now how should i do to use LWP::Simple. Can you provide me a demo of this algo. Second, the output come from http://localhost:3456 is an " unformatted XML". and I'm wondering if the Machine B gives its result because Perl is not installed in it.	[reply]
Re^3: Get into the server and execute perl command by Corion (Patriarch) on Feb 25, 2015 at 07:57 UTC
I suggest that you read the documentation of LWP::Simple. I'm not sure what other things you would need. This is not a code writing service. Also, I do not understand what you mean by "unformatted XML", and how it would be problematic.	[reply]
Re: Get into the server and execute perl command by GotToBTru (Prior) on Feb 24, 2015 at 16:21 UTC
Because your target is Windows, I would suggest looking into psexec, which can be run in Perl using the system command. See (OT) executing a command on a remote Windows XP machine Dum Spiro Spero	[reply]
Re^2: Get into the server and execute perl command by Anonymous Monk on Feb 24, 2015 at 17:44 UTC
I am making a spam bot. Thank you for helping.	[reply]
Re: Get into the server and execute perl command by karlgoethebier (Abbot) on Feb 25, 2015 at 13:23 UTC
"...two windows machines, one has perl installed, say machine A and other dont have perl, say Machine B. I want to go into the machine B..." Some half-cocked thoughts: Windows PowerShell Scripting with Windows PowerShell Running Remote Commands Invoke-Command pl2bat Best regards, Karl ŤThe Crux of the Biscuit is the Apostropheť	[reply]