Re: Procedure for handling actively exploited security bugs with patches?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "SG" == Steve Grubb <sgrubb@xxxxxxxxxx> writes:

SG> Security patches need careful but timely review. I recommend that
SG> the security team coordinate the repair and no one apply
SG> unreviewed patches just because you have access.

Oh, of course we can't trust the community here.  What was I thinking?
The security team, who in most cases doesn't even use the software in
question, is in a far better position to evaluate and test fixes than
someone who is actively interested in and familiar with the software.

 - J<

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux