On Wed, Aug 29, 2007 at 09:48:18PM -0400, Matt wrote:
> I've seen one too many "security upgrades" take a system
> down because they induced new bugs.
In this case, do a bit of extra work, and patch your version. Finding
the exact SVN commit that fixed the security issue is normally quite
easy, becase the commit message gets marked with a reference to the
respective ASA (Asterisk Security Anouncement).
You'll probably have to take some more time to actually read that ASA,
understand if it impacts your system, generate a patch and test it.
You would be deviating from the released version. Sure.
But then again, you always have the alternative of upgrading to the
latest version, which has been tested to fix the issue.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
