home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!gatech!psuvax1!mchen
- From: mchen@uranus.cs.psu.edu (Michael Chen)
- Newsgroups: comp.lang.tcl
- Subject: Re: Insecurity of tk
- Message-ID: <BzonE9.AFn@cs.psu.edu>
- Date: 22 Dec 92 22:49:18 GMT
- References: <1992Dec22.212801.6306@twg.com>
- Sender: news@cs.psu.edu (Usenet)
- Lines: 18
- In-Reply-To: "David Herron"'s message of Tue, 22 Dec 1992 21:28:12 GMT
- Nntp-Posting-Host: uranus.cs.psu.edu
-
-
- I assume that somewhere in the send command is a link to the interp that
- sent it. Why not set up a regexp pattern to match the requesting interp's name
- against, and to fail the send with some informative message if the regexp
- doesn't match? (Better, a list of regexps to try.)
- If it was initialized to *, that would match anything (default); that means
- that a security enforcing interp could do a send which would set the security
- (say accessible by "info security") to only match itself. Then you could
- handle it / monitor it with another interpreter, which presumably wouldn't
- take sends from anyone.
-
- -- Mike
- --
- _____________________________________________________________________________
- | Michael Chen | From the depths of our most lucid horrors |
- | | spring our fond hopes and pure desires... |
- | mchen@cs.psu.edu | except what comes from HELL! :-) 7/23/92 |
- \_______________________________\___________________________________________|
-