Hi again Trevor,

I agree that the best solution for SCROLLPrompt is for WebShell to
override it.

Having WebShell security tied to the operating system security has
advantages and disadvantages. You stated some of the advantages. But
some of the disadvantages are:

1) There is no security mechanism (e.g., login) for single user systems,
   like OS/2, unless you count the telnet password.

2) The user's login password would then be going over the network to
   authenticate WebShell, so there is much more at stake if the login
   password gets compromised. With a separate WebShell authentication,
   the worse that can happen if the WebShell password gets compromised
   is that a malicious user can backup/restore user's A files from/to
   user's A machine. The malicious user can not steal A's files or erase
   them, ...

3) It is not a consistent solution across all platforms and it would
   require WebShell to be much more platform dependent.

 Joann Ruvolo                             IBM Almaden Research Center
 VNET:     RUVOLO@ALMADEN                 K56/803              (tie) 457-1450
 Internet: ruvolo AT almaden.ibm DOT com         650 Harry Road       (408) 
927-1450
 E Mail:   ruvolo AT zorg.almaden.ibm DOT com    San Jose, CA 95120   (fax) 
927-2100