On Mon, Nov 07, 2011 at 08:37:55PM -0700,
brian nikell nickell...@gmail.com wrote
a message of 38 lines which said:
Actually, Juniper does disclose code bugs. Though not always to the
public at first, importantly to Juniper customers. Juniper had
advised all of their customers last August
Stephane Bortzmeyer bortzme...@nic.fr writes:
(Given the
complexity of conditions required to trigger this issue, the
probability of exploiting this defect is extremely low).
Which translates to
This bug has such catastrophic consequenses that we do not want to
disclose how to trigger it.
On Tue, 08 Nov 2011 09:21:37 +0100, Stephane Bortzmeyer said:
I disagree. The official bug statement from Juniper in August was
trying very hard to downplay the importance of the bug (Given the
complexity of conditions required to trigger this issue, the
probability of exploiting this defect
On 11/8/2011 12:05 PM, valdis.kletni...@vt.edu wrote:
And if JunOS is anything like CIsco IOS, a lot of shops didn't upgrade because
the newer release has *other* issues in their environments. Nobody wants to
upgrade to fix a once-ever-few-months bug if it also buys them a daily crash in
- Original Message -
From: Jonathan Lassoff j...@thejof.com
tangential sidenote
It's too bad that Junipers bugs aren't listed publicly. For clueful
network operations, having this information available to them could
have enabled them to properly weigh the risk of evaluating and
Actually, Juniper does disclose code bugs. Though not always to the public
at first, importantly to Juniper customers. Juniper had advised all of
their customers last August of this bug, however Level3 chose to continue
running it on their peer routers. Thus if Level3 and its clue(full)
management
6 matches
Mail list logo
