On Sat, 2003-08-23 at 19:28, Mark Steward wrote:
> > Perhaps I'm confused about how the clipboard redirector works; One of
> > the goals involves not installing anything on the windows server.
> Fair enough. But isn't creating a .vbs file tantamount to installing
> something?
Perhaps in some peoples mind; it is worth mentioning that I don't have
to install the .vbs _before_ the procedure begins - i.e. it's installed
via robot remotely using the existing channels. This is acceptable,
albeit just barely.
> Other (hack) options would be using a file over RDP shared
> drives to control the command prompt. This could easily be written in a
> VBScript file. You could even use a virtual printer.
Is this actually documented for a VBS interface in MSDN someplace? I
find that site a nightmare to browse as I can't ever be sure if reading
a page will prevent me from implementing it :)
> > Another one (not mentioned) is that I'm not going to use any additional
> > network connections.
> Does that mean no channels (as channels are built into RDP)?
No it does not mean that. It does mean that if I connect through a NAT
to a dmz-mapped terminal server there is no way that the terminal server
nor my workstation can guarantee that they can communicate with
each-other over any other connection. This negates the possibility of
pushing a program to download a proper .exe for the target.
> > Regarding the dialog box: very easy to avoid actually, simply do what
> > I'm doing now- discard the text in a font that I don't expect (or
> > haven't synchronized to).
> How about if that dialog box is on top of your command prompt? A GUI
> expects an intelligent user, not an OCR script.
I agree; it isn't the _best option_, but until the vbs bootstrap is
pushed, or we can get the literal text strings/position+fonts we can
probably say "it's okay" if the initial connection startup is not quite
as stable- e.g. someone sends a winpopup message after logging in, but
before the cmd.exe starts up-or after text sync occurs but before
bootstrapping. these cases are not completely improbable, but we can
build special cases to work around them.
Later RDP versions talk about the client pushing a theme, perhaps this
means we can paint dialogs a special color and when seeing them select
the less dangerous of the buttons (cancel, etc)
> Isn't it better to keep it
> simple?
I agree :)
> You could set the program to run through RDP, and so minimise risk
> from complicated programs like Explorer. Would you like a basic example
> program?
I already do; I start cmd.exe as the shell (i believe I mentioned this
on earlier posts), and intended to communicate with that window.
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
|
