Workspace launched from remote terminal

karron at MCIRPS2.MED.NYU.EDU karron at MCIRPS2.MED.NYU.EDU
Wed Aug 15 16:40:10 AEST 1990


jdm at boulder.colorado.edu writes:
>       When someone is logged onto the console, and a remote
>user starts up a gl program, it gets sent to the console.
>       One of our users has something set so that when he logs
>in remotely, his workspace appears on the console.
>
>       Is there anyway to prevent these things from happening?
>Its rather disconcerting to the console user, not to mention somewhat
>of a security problem...
>

Yes.

I have found two ways.

1) startup workspace from your user.ps or startup.ps files.  The incantation
was posted some time ago, and I will get it for you if you want it.  The good
news is that the shell containing workspace will ONLY start if you own the gl
window.  The problem is that the shell you start from postscript will be run
prior to your .login and .cshrc, and will not be a child process that will
know anything from your .login.  Some people have complained that an editor
started from workspace in this way will not know what term to use or which
printer to use if you depending on setting these vars in your .login .

2) startup workspace in your .login, and run it only if your TERM is the
iris-ansi and your REMOTEHOST is not set. There are many other hacks to
test where you are logging in from. The problem with this is that you
have to test if workspace is running already, or every new window you
open will also run .login and workspace will intrude itself onto your
window after you have pushed it below other windows.

dan.

+-----------------------------------------------------------------------------+
| karron at nyu.edu                          Dan Karron                          |
| . . . . . . . . . . . . . .             New York University Medical Center  |
| 560 First Avenue           \ \    Pager <1> (212) 397 9330                  |
| New York, New York 10016    \**\        <2> 10896   <3> <your-number-here>  |
| (212) 340 5210               \**\__________________________________________ |
+-----------------------------------------------------------------------------+



More information about the Comp.sys.sgi mailing list