Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
I have a customer that is unhappy with the fact that when the session manager is killed that this opens up all windows even though the workstation had been paused. In his case, the system manager killed the session manager so that the UAF could be moved. He feels that this is something of a security hole and would like to have me make the developers aware of the situation and find out if there is anything that can be done. I pointed out that this could only be done by a suitably privileged process and that that process had the system by the throat anyway. He agreed and was resigned to the possibility that there might not be anything that could be done but asked that I make the developers aware of his concerns anyway. I decided the best way to do this would be through this notes conference. Any comments, ideas, or suggestions would be very much appreciated. Regards, -Tom
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2597.1 | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Wed Apr 11 1990 13:59 | 7 | |
I don't know that there is much to be said or done about this. The session mgr is what implements pause. If you stop it, it goes away. Pause is essentially a new feature. If he wants to get back to the old (and in his opinion more secure) way of doing business, then he has to tell everyone to log out rather than pause. Burns | |||||
2597.2 | PSW::WINALSKI | Careful with that VAX, Eugene | Wed Apr 11 1990 17:22 | 11 | |
RE: .0 >In his case, the system manager killed the session manager >so that the UAF could be moved. I don't understand why the session manager had to be killed to move the UAF. Basically, this is a case of "Doctor, it hurts when I shoot myself in the foot." --PSW |