Chip 2000 May

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 May / Chip_2000-05_cd1.bin / zkuste / Perl / ActivePerl-5.6.0.613.msi / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _e47756fc3f15bbd407886fadebd32e8d < prev next >

Wrap

Text File | 2000-03-23 | 7KB | 149 lines

<HTML> <HEAD> <TITLE>send - Execute a command in a different application</TITLE> <LINK REL="stylesheet" HREF="../../../Active.css" TYPE="text/css"> <LINK REV="made" HREF="mailto:"> </HEAD> <BODY> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> send - Execute a command in a different application </TD></TR> </TABLE> <A NAME="__index__"></A>  <UL> <LI><A HREF="#name">NAME</A></LI><LI><A HREF="#supportedplatforms">SUPPORTED PLATFORMS</A></LI> <LI><A HREF="#synopsis">SYNOPSIS</A></LI> <LI><A HREF="#description">DESCRIPTION</A></LI> <LI><A HREF="#application names">APPLICATION NAMES</A></LI> <LI><A HREF="#what is a send">WHAT IS A SEND</A></LI> <LI><A HREF="#security">SECURITY</A></LI> <LI><A HREF="#see also">SEE ALSO</A></LI> <LI><A HREF="#keywords">KEYWORDS</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> send - Execute a command in a different application <HR> <H1><A NAME="supportedplatforms">SUPPORTED PLATFORMS</A></H1> <UL> <LI>Linux</LI> <LI>Solaris</LI> <LI>Windows</LI> </UL> <HR> <H1><A NAME="synopsis">SYNOPSIS</A></H1> $result = $widget->send(?options,?app=>cmd?arg arg ...?) <HR> <H1><A NAME="description">DESCRIPTION</A></H1> This method arranges for cmd (and args) to be 'sent' to the application named by app. It returns the result or an error (hence above should probably be 'wrapped' in eval{} and $@ tested). App may be the name of any application whose main window is on the display containing the sender's main window; it need not be within the same process. If no arg arguments are present, then the string to be sent is contained entirely within the cmd argument. If one or more args are present, they are concatenated separated by white space to form the string to be sent. If the initial arguments of the call begin with ``-'' they are treated as options. The following options are currently defined: <DL> <DT><A NAME="item_%2Dasync">-async</A> <DD> Requests asynchronous invocation. In this case the send command will complete immediately without waiting for cmd to complete in the target application; no result will be available and errors in the sent command will be ignored. If the target application is in the same process as the sending application then the -async option is ignored. <DT><A NAME="item_%2D%2D">--</A> <DD> Serves no purpose except to terminate the list of options. This option is needed only if app could contain a leading ``-'' character. </DL> <HR> <H1><A NAME="application names">APPLICATION NAMES</A></H1> The name of an application is set initially from the name of the program or script that created the application. You can query and change the name of an application with the appname method. <HR> <H1><A NAME="what is a send">WHAT IS A SEND</A></H1> The send mechanism was designed to allow Tcl/Tk applications to send Tcl Scripts to each other. This does not map very well onto perl/Tk. Perl/Tk ``sends'' a string to app, what happens as a result of this depends on the receiving application. If the other application is a Tcl/Tk4.* application it will be treated as a Tcl Script. If the ``other'' application is perl/Tk application (including sends to self) then the string is passed as an argument to a method call of the following form: $mainwindow->Receive(string); There is a default (AutoLoaded) Tk::Receive which returns an error to the sending application. A particular application may define its own Receive method in any class in MainWindow's inheritance tree to do whatever it sees fit. For example it could eval the string, possibly in a Safe ``compartment''. If a Tcl/Tk application ``sends'' anything to a perl/Tk application then the perl/Tk application would have to attempt to interpret the incoming string as a Tcl Script. Simple cases are should not be too hard to emulate (split on white space and treat first element as ``command'' and other elements as arguments). <HR> <H1><A NAME="security">SECURITY</A></H1> The send command is potentially a serious security loophole, since any application that can connect to your X server can send scripts to your applications. Hence the default behaviour outlined above. (With the availability of Safe it may make sense to relax default behaviour a little.) Unmonitored eval'ing of these incoming ``scripts'' can cause perl to read and write files and invoke subprocesses under your name. Host-based access control such as that provided by xhost is particularly insecure, since it allows anyone with an account on particular hosts to connect to your server, and if disabled it allows anyone anywhere to connect to your server. In order to provide at least a small amount of security, core Tk checks the access control being used by the server and rejects incoming sends unless (a) xhost-style access control is enabled (i.e. only certain hosts can establish connections) and (b) the list of enabled hosts is empty. This means that applications cannot connect to your server unless they use some other form of authorization such as that provide by xauth. <HR> <H1><A NAME="see also">SEE ALSO</A></H1> Perl's eval perl's Safe Module system's administrator/corporate security guidelines etc. <HR> <H1><A NAME="keywords">KEYWORDS</A></H1> application, name, remote execution, security, send <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> send - Execute a command in a different application </TD></TR> </TABLE> </BODY> </HTML>