|
|
发表于 2010-4-19 12:22:31
|
显示全部楼层
http://www.debian.org/security/
http://www.debian.org/security/faqQ: How is security handled for unstable?
A: The short answer is: it's not. Unstable is a rapidly moving target and the security team does not have the resources needed to properly support it. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable.
Q: How is security handled for testing?
A: If you want to have a secure (and stable) server you are strongly encouraged to stay with stable. However, there is security support for testing: The Debian testing security team handles issues for testing. They will make sure that the fixed packages enter testing in the usual way by migration from unstable (with reduced quarantine time), or, if that still takes too long, make them available via the the normal http://security.debian.org infrastructure. To use it, make sure the following line is in /etc/apt/sources.list:
deb http://security.debian.org testing/updates main
and run apt-get update && apt-get upgrade as usual.
Note that this doesn't guarantee that all known security bugs are fixed in testing! Some updated packages might be waiting for transition to testing. More information about the security infrastructure for testing can be found at http://secure-testing-master.debian.net/.
Q: How is security handled for contrib and non-free?
A: The short answer is: it's not. Contrib and non-free aren't official parts of the Debian Distribution and are not released, and thus not supported by the security team. Some non-free packages are distributed without source or without a license allowing the distribution of modified versions. In those cases no security fixes can be made at all. If it is possible to fix the problem, and the package maintainer or someone else provides correct updated packages, then the security team will generally process them and release an advisory. Security support for testing
The team is providing security support for Debian's testing branch by
* writing patches and doing NMUs to unstable as necessary
* tracking the fixed packages and working with the Debian Release Managers to make sure fixes reach testing quickly
* if this process is too slow, providing fixed packages built against testing in the testing-security apt repository:
deb http://security.debian.org squeeze/updates main contrib non-free
deb-src http://security.debian.org squeeze/updates main contrib non-free
However, the majority of security fixes reach testing by migration from unstable.
Note that in order to take advantage of the security support for testing, you must update your system on a regular basis.
Limitations
For several reasons, the security support for testing cannot be expected to be of the same quality as for Debian's stable branch:
* Updates for testing-security usually receive less testing than updates for stable-security.
* Testing is changing all the time which increases the likelihood of problems with the build infrastructure. Such problems can delay security updates in testing. |
|
IP卡
狗仔卡
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡
楼主