Development procedures Debian
each software package has maintainer may either 1 person or team of debian developers , non-developer maintainers. maintainer keeps track of upstream releases, , ensures package coheres rest of distribution , meets standards of quality of debian. packages may include modifications introduced debian achieve compliance debian policy, fix non-debian specific bugs, although coordination upstream developers advised.
the maintainer releases new version uploading package incoming system, verifies integrity of packages , digital signatures. if package found valid, installed in package archive area called pool , distributed every day hundreds of mirrors worldwide. upload must signed using openpgp-compatible software. debian developers have individual cryptographic key pairs. developers responsible package upload if packaging prepared contributor.
initially, accepted package available in unstable branch. package become candidate next release, must migrate testing branch meeting following:
it has been in unstable length of time depends on urgency of changes.
it not have release-critical bugs, except ones present in testing. release-critical bugs considered serious enough make package unsuitable release.
there no outdated versions in unstable release ports.
the migration not break packages in testing.
its dependencies can satisfied packages in testing or packages being migrated @ same time.
the migration not blocked freeze.
thus, release-critical bug in new version of shared library on many packages depend may prevent packages entering testing, because updated library must meet requirements too. branch viewpoint, migration process happens twice per day, rendering testing in perpetual beta.
periodically, release team publishes guidelines developers in order ready release. new release occurs after freeze, when important software reasonably up-to-date in testing branch , other significant issues solved. @ time, packages in testing branch become new stable branch. although freeze dates time-based, release dates not, announced release managers couple of weeks beforehand.
a version of package can belong more 1 branch, testing , unstable. possible package keep same version between stable releases , part of oldstable, stable, testing , unstable @ same time. each branch can seen collection of pointers package pool mentioned above.
security
the debian project handles security through public disclosure rather through obscurity. debian security advisories compatible common vulnerabilities , exposures dictionary, coordinated other free software vendors , published same day vulnerability made public. there used security audit project focused on packages in stable release looking security bugs; steve kemp, started project, retired in 2011 resumed activities , applied rejoin in 2014.
the stable branch supported debian security team; oldstable supported 1 year. although squeeze not officially supported, debian coordinating effort provide long-term support (lts) until february 2016, 5 years after initial release, ia-32 , x86-64 platforms. testing supported testing security team, not receive updates in timely manner stable. unstable s security left package maintainers.
the debian project offers documentation , tools harden debian installation both manually , automatically. security-enhanced linux , apparmor support available disabled default. debian provides optional hardening wrapper, , not harden of software default using gcc features such pie , buffer overflow protection, unlike operating systems such openbsd, tries build many packages possible hardening flags.
2008 openssl vulnerability
in may 2008, revealed debian developer discovered openssl package distributed debian , derivatives such ubuntu, made variety of security keys vulnerable random number generator attack, since 32,767 different keys generated. security weakness caused changes made in 2006 debian developer in response memory debugger warnings. complete resolution procedure cumbersome because patching security hole not enough; involved regenerating affected keys , certificates.
Comments
Post a Comment