[709] in WWW Security List Archive
Re: Overlapping lists
daemon@ATHENA.MIT.EDU (Prentiss Riddle)
Wed May 17 14:41:47 1995
From: riddle@is.rice.edu (Prentiss Riddle)
To: alex@virtual.office.com
Date: Wed, 17 May 1995 08:34:30 -0500 (CDT)
Cc: e-payment@ccbellcore.com, www-security@ns2.rutgers.edu,
www-buyinfo@allegra.att.com
In-Reply-To: <Pine.3.89.9505161127.C5551-0100000@virtual.office.com> from "S. Alexander Jacobson" at May 16, 95 11:38:56 am
Errors-To: owner-www-security@ns2.rutgers.edu
> Date: Tue, 16 May 1995 11:38:56 -29900
> From: "S. Alexander Jacobson" <alex@virtual.office.com>
> Subject: Overlapping lists
> To: e-payment@ccbellcore.com, www-security@ns2.rutgers.edu,
> www-buyinfo@allegra.att.com
>
> Is there a reason for three separate completely overlapped lists on the
> same topic? Can we merge them into one list?
>
> If not, can someone enunciate some clear principles for differentiating
> what should be on each list?
I don't know about the other two, but the www-security list has a very
important function which overlaps only minimally with the subject of
e-payment: to discuss security holes in HTTP servers and clients and
how to fix them.
I agree that moving e-payment traffic out of www-security and into the
other list(s) might be a good idea, if only because it will create a
less noisy place in which to discuss security-related WWW bugs. The
WWW development community doesn't seem to participate in the
www-security list as it should, perhaps because the list isn't focused
on the security of *existing* WWW software.
For the same reason, I would oppose simply merging all three lists.
-- Prentiss Riddle ("aprendiz de todo, maestro de nada") riddle@rice.edu
-- Systems Programmer and RiceInfo Administrator, Rice University
-- 2002-A Guadalupe St. #285, Austin, TX 78705 / 512-323-0708
