- From: Thomas Roessler <tlr@w3.org>
- Date: Tue, 21 Nov 2006 17:15:39 +0100
- To: Web Security Context Issue Tracker <dean+cgi@w3.org>
- Cc: public-wsc-wg@w3.org
This takes care of ACTION-35. -- Thomas Roessler, W3C <tlr@w3.org> On 2006-11-21 16:14:28 +0000, Web Security Context Issue Tracker wrote: > From: Web Security Context Issue Tracker <dean+cgi@w3.org> > To: public-wsc-wg@w3.org > Date: Tue, 21 Nov 2006 16:14:28 +0000 (GMT) > Subject: ISSUE-4: How applicable is baseline information to content > retrieved by FTP? > Reply-To: Web Security Context WG <public-wsc-wg@w3.org> > List-Id: <public-wsc-wg.w3.org> > X-Spam-Level: > X-Archived-At: http://www.w3.org/mid/20061121161428.8B918BDA8@w3c4.w3.org > > > > ISSUE-4: How applicable is baseline information to content retrieved by FTP? > > http://www.w3.org/2006/WSC/Group/track/issues/4 > > Raised by: Stephen Farrell > On product: Security Baseline Information > > On 2006-11-21, the group agreed to keep HTTP at the center of its work. Stephen > Farrell raised that retrieval of content by FTP might lead to new holes. The > group is expected to review this topic again as it gets to some substance on its > security baseline deliverable. > > ACTION-32 [1] is expected to lead to a use case narrative that will be useful in > this exercise. > > 1. http://www.w3.org/2006/WSC/track/actions/32 > > > >
Received on Tuesday, 21 November 2006 16:15:52 UTC