[2528] in SIPB bug reports

home help back first fref pref prev next nref lref last post

Re: new xscreensaver feature

daemon@ATHENA.MIT.EDU (web@Athena.MIT.EDU)
Fri Feb 28 15:38:42 1992

From: web@Athena.MIT.EDU
To: jtidwell@Athena.MIT.EDU
Cc: bug-sipb@Athena.MIT.EDU
In-Reply-To: Your message of Fri, 28 Feb 92 15:09:09 -0500.
Date: Fri, 28 Feb 92 15:37:15 EST


Jenifer, this was originally to bug-sipb, not to sipb.

The difference is that in most of the other cases, you mentioned, people
don't have much of an alternative.

>   Social problem:  people breaking into each others' accounts
>   Software solution:  password encryption, Kerberos, etc.
> 

People must to use kerberos, or else they can't log in.

>   Social problem:  overuse of disk space
>   Software solution:  disk quotas
> 

People are forced to have a disk quota unless they provide their own
server (in which case it's ok)

>   Social problem:  abuse of printing privileges
>   Software solution:  print quotas
> 

People are forced to abide by the quota unless they have a private printer.

>   Social problem:  people spending too much idle time on dialup machines
>   Software solution:  the idle gunner

They have no other dialup to go to.

> 
>   Social problem:  Xtrek taking up too much net bandwidth
>   Software solution:  can only play an opponent on the same subnet
> 

Actually, there are modified Xtreks around which cross the subnet.  But
the limiting thing is that Xtrek is quite a large program.

>   Social problem:  people make zephyrgrams beep too much
>   Software solution:  a sequence of @beep()'s can now make only one beep
> 

The receiving zwgc is the limiting one, so the attacker has no control
or ability to hose others.

>   Social problem:  abuse of xscreensaver to hold an idle workstation 
>   Software solution:  anyone can log you out after a time limit

This is different.  We cannot force people to use our version as has
been done with the examples you provided.

Consider also:

Social problem: abuse of dialups sending windows everywhere
Software solution: try to fake them out with a new emacs.
Work around: send windows anyways (find the real emacs).  Run maple,
matlab, even xconq. 

The point is that if an alternate route is provided, users will take it.
An alternate route is available for our screensaver.  

I believe jik's solution is likely the best so far.

-Chee

home help back first fref pref prev next nref lref last post