Secure testing team - May 2008 - Seems fixed in the wrong place

Hi,
> please CC secure-testing-team at lists.alioth.debian.org in the case of a
> security related bug and if the version of that bug is also in testing.
I''m not so sure this is a good idea. We now have reportbug adding a CC
when a bug is reported with that tag, reportbug-ng being patched to do the
same, and the bts command changed so it CC''s the teams when someone
adds
such a tag. However, it completely misses those cases where someone just
mails submit@ or control@ directly (quite common), or any new or custom
tools that may arise.

Why don''t we just reassign this bug to the BTS and have request that
changed so that it forwards those bugs to the specific place? It''s the
canonical place, it''s one place to change when changes are needed and
it
will work regardless of which bug reporting method someone chooses.


Thijs

Hi Thijs,
* Thijs Kinkhorst <thijs at debian.org> [2008-05-23
11:40]:
> > please CC secure-testing-team at lists.alioth.debian.org in the case
of a
> > security related bug and if the version of that bug is also in
testing.
> 
> I''m not so sure this is a good idea. We now have reportbug adding
a CC
> when a bug is reported with that tag, reportbug-ng being patched to do the
> same, and the bts command changed so it CC''s the teams when
someone adds
> such a tag. However, it completely misses those cases where someone just
> mails submit@ or control@ directly (quite common), or any new or custom
> tools that may arise.
> 
> Why don''t we just reassign this bug to the BTS and have request
that
> changed so that it forwards those bugs to the specific place? It''s
the
> canonical place, it''s one place to change when changes are needed
and it
> will work regardless of which bug reporting method someone chooses.
Sounds way more sane, I filed a wishlist bug against 
bugs.debian.org

Kind regards
Nico
-- 
Nico Golde - http://www.ngolde.de - nion at jabber.ccc.de - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/secure-testing-team/attachments/20080523/c783dfd7/attachment.pgp

* Thijs Kinkhorst:
> Why don''t we just reassign this bug to the BTS and have request
that
> changed so that it forwards those bugs to the specific place? It''s
the
> canonical place, it''s one place to change when changes are needed
and it
> will work regardless of which bug reporting method someone chooses.
Is this really necessary?  After all, you can subscribe to bugs-dist and
filter on your own.

Hi Florian,
* Florian Weimer <fw at deneb.enyo.de> [2008-05-24
23:47]:
> * Thijs Kinkhorst:
> 
> > Why don''t we just reassign this bug to the BTS and have
request that
> > changed so that it forwards those bugs to the specific place?
It''s the
> > canonical place, it''s one place to change when changes are
needed and it
> > will work regardless of which bug reporting method someone chooses.
> 
> Is this really necessary?  After all, you can subscribe to bugs-dist and
> filter on your own.
That''s also what I am doing right now but that''s quite a 
bunch of mails every day and the chance to miss anything is 
not that low :/
Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - nion at jabber.ccc.de - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/secure-testing-team/attachments/20080525/e7c80895/attachment.pgp