James,Great, however the question has been answered, when is this going to be pushed out ? What is the date ?
Most repositories when a security issue has been identified and fixed, its pushed so that updaters can take advantage of it.
The patch if not applied correctly, it will create more support problems then the fix it provides. Is Opsview team going to stop and help people trying to fix the problems created by applying the patch wrong ?
Cheers, Roberto--On October 8, 2010 6:45:25 PM +0100 James Peel <[email protected]> wrote:
Hi If this is a security fix, which it is, why is opsview team not pushing this out ? When you are going to push this out ? Ton posted a link to the code fix on the opsview-users list earlier so that you can patch critical systems:https://secure.opsera.com/wsvn/wsvn/opsview?op=comp&compare[]=%2Ftru n...@5159&compare[]=%2ftr...@5160 So, the fix is already available in trunk and will be included in 3.9.1 / 3.10.0 To check out the code from subversion: $ svn co https://secure.opsera.com/svn/opsview/trunk opsview -- James
-- -------------------------------- Roberto R. Morelli [email protected] Energy Sciences Network Lawrence Berkeley National Lab. 510-486-7255 PGP Key Fingerprint: F49F 1186 0E2B F591 1BF7 0538 79AA F8C7 7E8B 4562
pgpTjK5j9y6A5.pgp
Description: PGP signature
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
