Remote sh via HTTP>>>> net view Server Name Remark ------------------------------------------------------------------------------- \\DOUG \\ENTERPRISE \\NT-NITES \\PCGINT The command completed successfully. >>>> dir \\enterprise\temp Volume in drive \\enterprise\temp is MICRON Volume Serial Number is 4109-1B07 Directory of \\enterprise\temp 09/02/97 01:08a <DIR> . 09/02/97 01:08a <DIR> .. 04/28/98 04:49p 10,752 ~DFD6F2.tmp 04/27/98 04:22p 10,752 ~DF6E4A.tmp 04/28/98 06:34a 0 ~DFD760.tmp 03/09/98 11:45a 1,099 mso254.csv 12/23/97 08:05a <DIR> VBE 04/29/98 06:36a 10,752 ~DF8987.tmp 04/29/98 06:36a 0 ~DF89C3.tmp |
The "frameset" above is a "snapshot" of a remote shell session, from a browser running on a Mac displaying a form off a HTTP server running on a Linux box; the form's ACTION
is a do-sh.pl
script on a WinNT server.
Although this remote shell facility has little to do with HTTP VFS, they are related. They both show off HTTP. I must disclaim: this
facility is not a telnet as it does not maintain the current directory
and other environment, yet. Still do-sh.pl
does maintain a session
log, of all executed commands and their results. Again, the script
runs under UNIX as well as WinNT. Thus you can execute 'net view
',
'net users
', 'net share
', 'dir \\enterprise\temp
', 'del
', etc. WinNT
commands on a target computer from any Web browser. Provided that the
target box grants the necessary privileges to do-sh.pl
- to the user
actually on whose behalf the script is run; the security section above has discussed these matters.
The vfs-client/VFS-server pair can also be used outside of MC. For
example, to implement rls
(remote ls) and rcp
(remote copy). Again, a remote end does not have to be a UNIX box. Nor does the local end: the
vfs-client
runs on WinNT/Win95 as well. Thus one can turn the tables
and command UNIX boxes from, for example, .BAT
scripts.