🚀 go-pugleaf

danj1@ihspa.ATt.COM (Dan Jacobson) writes
> login should be a builtin, because if jimmy, used to some other leading
> brands of shell, does
> bash$ login jenny
> as he turns over the terminal to jenny, and then later jenny logs out
> and walks away, jimmy's bash will be sitting there, so some baddie
> will take advantage of it

  [ deleted ]

> Plus it's unreasonable to expect jimmy to memorize "'exec login' when
> under bash".

It's unreasonable for jenny not to expect a trojan horse when jimmy types
	bash$ login jenny
at his terminal and then says "there you go, it's all yours".  Both
jimmy and jenny appear to be in dire need of a basic computer security
course.  Even something as simple as:
	1. "always log out when you leave your terminal"
	2. "never log in unless you're sure a trojan isn't running"**
would do.  If they can't even master these basic points, they have a
whole heap more trouble to worry about than login not being a builtin
in some shells. 

Jonathan H.

** For arbitrary definitions of "sure".