I agree that both mechanisms should be supported, I think that makes
the most sense.
Your tunnel app sounds cool, and desperately needed!
Jason
On Dec 21, 2004, at 1:30 AM, Sean Kamath wrote:
>
> Hi.
>
> I'm writing a simple little SSH tunnel app (using Perl, Platypus and
> CocoaDialog, no less), and am now at that point where I'm ready to
> tell cotvnc open a connection to localhost:<port>.
>
> When the AppleScript is all there, I can use it to tell a running
> CotVNC to open a connection (I hope), but I'll want to tell is
> specifically to open localhost:<display>, not using a profile (since
> the local port will change, depending on how many I have running.
>
> Alternatively, and prefered, is to use the command line. There are
> two issues with that: 1) You'll have multiple CotVNC's running in the
> dock -- yuk. 2) (and this is currently nasty), there's no easy way to
> specify a password or tell the opening CotVNC to present a password
> dialog box.
>
> Personally, I think both mechanisms should be supported (AppleScript
> to tell CotVNC to open a host:port with optional profile, but not
> saving it in the server list; Command line to open a connection and
> take a cleartext password on stdin or present a dialog box).
>
> Thoughts?
>
> Sean
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> cotvnc-devel mailing list
> cotvnc-devel@...
> https://lists.sourceforge.net/lists/listinfo/cotvnc-devel
>
>
|