Re: Patch management tool

It's called back porting. The reason they do it is because it makes QA a 
heck of a lot easier, imagine OpenSSH 3.5 -> 3.6 vs.s. OpenSSH 3.5 -> 
OpenSSH 3.5 plus a 50 line patch. Which is less likely to behave in new (an 
unexpected) ways? It also makes customers a lot easier, I have a commercial 
app that depends on version X of foo, now it may work with version X.1, but 
it might not. Personally I'd rather not find out. Back porting is the only 
sane alternative if you have several hundred packages that require active 
maintenance, QA, and don't want to annoy customers.

Kurt Seifried, kurt@seifried.org
A15B BEE5 B391 B9AD B0EF
AEB0 AD63 0B4E AD56 E574
http://seifried.org/security/




------------------------------------------------------------------------------
Ethical Hacking at the InfoSec Institute. All of our class sizes are
guaranteed to be 12 students or less to facilitate one-on-one interaction
with one of our expert instructors. Check out our Advanced Hacking course,
learn to write exploits and attack security infrastructure. Attend a course
taught by an expert instructor with years of in-the-field pen testing
experience in our state of the art hacking lab. Master the skills of an
Ethical Hacker to better assess the security of your organization.

http://www.infosecinstitute.com/courses/ethical_hacking_training.html
-------------------------------------------------------------------------------