[Secure-testing-team] Security update for fuse

[Micah Anderson]

This thread brings up something that has not been worked out here in
the testing-security team. We need to define some procedures for
handling this sort of thing that can be made public so developers know
what to do. 

Additionally, should testing-security provide security notices (such
as DSA's)? If so, how would this work?

It has been asked on debian-security, and debian-devel[1] what
testing-security has done. Thus far, we have only been tracking known
CAN/DSAs and generating the newraff/~joeyh/testing-security.html page.
This page is useful for release managers, and people concerned about
running testing (and arguably a blueprint/roadmap for hackers, but
thats another thread). But are people expecting more? If so what is
it? Security updates have been going through unstable, or
testing-proposed-updates, supposedly there was some testing-security
infrastructure that was holding up sarge, but we aren't really using
it.

Micah

1. http://lists.debian.org/debian-devel/2005/05/msg01060.html


On Sat, 04 Jun 2005, Martin Schulze wrote:

> If it should go via security.debian.org, I'll just fetch the source
> package, strip off the unstable part, rebuild as 2.2.1-4sarge1 and
> take care of it.
> 
> Regards,
> 
> 	Joey
> 
> -- 
> Those who don't understand Unix are condemned to reinvent it, poorly.
> 
> _______________________________________________
> Secure-testing-team mailing list
> Secure-testing-team at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/secure-testing-team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/secure-testing-team/attachments/20050604/5efed5eb/attachment.pgp