* Paul Johnson <baloo@ursine.ca> [2006-05-27 01:07]: > > So it comes down to: > > * Is it a bad idea to use unstable on a production server > > when it comes to security? > > Possibly to probably yes (the answer for stable would be "no"). > > > * If so, would you recommend using testing, or stable? > > Stable. > > > * And does anyone with experience running unstable on production > > servers know of any other caveats I should be aware of? > > Don't do it unless you want to babysit it constantly and do a lot of > reading in your free time to keep track of development and latest > bugs a lot more carefully than you otherwise would. So just keeping up with debian security announcements wouldn't be enough? I would have to actively monitor security issues for the services the server provides? Or would it be enough to make sure I keep the server up-to-date and occasionally take it down to fix some debian-unstable-induced breakage to keep it secure? - Felix -- Felix C. Stegerman <flx@obfusk.net> http://obfusk.net ~ "Any sufficiently advanced bug is indistinguishable from a feature." ~ -- R. Kulawiec ~ vim: set ft=mail tw=70 sw=2 sts=2 et:
Attachment:
pgpt0vmxaYX9o.pgp
Description: PGP signature