Re: Juniper SSL VPN

2013-12-31 Thread Jamie Gwatkin
Could be related to this?
http://kb.juniper.net/InfoCenter/index?page=contentid=TSB16290


On Tue, Dec 31, 2013 at 10:31 AM, Sharma, Kapeel kapeel.sha...@mckesson.com
 wrote:

 Any one heard of a host checker issue with Juniper VPN today  ?

 Thanks
 Kapeel




RE: Juniper SSL VPN

2013-12-31 Thread Sharma, Kapeel
This is it thanks.

Kapeel

From: Jamie Gwatkin [mailto:jgwat...@magmic.com]
Sent: Tuesday, December 31, 2013 7:43 AM
To: Sharma, Kapeel
Cc: nanog@nanog.org
Subject: Re: Juniper SSL VPN

Could be related to this? 
http://kb.juniper.net/InfoCenter/index?page=contentid=TSB16290

On Tue, Dec 31, 2013 at 10:31 AM, Sharma, Kapeel 
kapeel.sha...@mckesson.commailto:kapeel.sha...@mckesson.com wrote:
Any one heard of a host checker issue with Juniper VPN today  ?

Thanks
Kapeel



Re: Juniper SSL VPN

2013-12-31 Thread Mike Hale
Wow.   Thanks for posting this.   I thought we were just going crazy
yesterday.
On Dec 31, 2013 7:45 AM, Jamie Gwatkin jgwat...@magmic.com wrote:

 Could be related to this?
 http://kb.juniper.net/InfoCenter/index?page=contentid=TSB16290


 On Tue, Dec 31, 2013 at 10:31 AM, Sharma, Kapeel 
 kapeel.sha...@mckesson.com
  wrote:

  Any one heard of a host checker issue with Juniper VPN today  ?
 
  Thanks
  Kapeel
 
 



Re: Juniper SSL VPN

2013-12-31 Thread Valdis . Kletnieks
On Tue, 31 Dec 2013 10:43:02 -0500, Jamie Gwatkin said:
 Could be related to this?
 http://kb.juniper.net/InfoCenter/index?page=contentid=TSB16290

Do I want to ask why *THIS*?

Estimated Fix Date:
Juniper engineering has root caused this issue is working to build and release
a ESAP fix as soon as possible. The initial estimated release date for the fix
is between 12/31/2013 (PST) and 1/3/2014 (PST). We will update this message
regularly with the current status until we resolve this issue.

We need an emergency fix because a piece of software unexpectedly hit
an end-of-life date?  Didn't we learn anything 14 years ago??!?



pgpbFl8yrGV6S.pgp
Description: PGP signature


Re: Juniper SSL VPN

2013-12-31 Thread Eugeniu Patrascu
On Tue, Dec 31, 2013 at 7:31 PM, valdis.kletni...@vt.edu wrote:

 On Tue, 31 Dec 2013 10:43:02 -0500, Jamie Gwatkin said:
  Could be related to this?
  http://kb.juniper.net/InfoCenter/index?page=contentid=TSB16290

 Do I want to ask why *THIS*?

 Estimated Fix Date:
 Juniper engineering has root caused this issue is working to build and
 release
 a ESAP fix as soon as possible. The initial estimated release date for the
 fix
 is between 12/31/2013 (PST) and 1/3/2014 (PST). We will update this message
 regularly with the current status until we resolve this issue.

 We need an emergency fix because a piece of software unexpectedly hit
 an end-of-life date?  Didn't we learn anything 14 years ago??!?


Juniper just posted a technical note saying the issue is fixed and a new
ESAP package is out.


Re: Juniper SSL VPN

2013-12-31 Thread Valdis . Kletnieks
On Tue, 31 Dec 2013 23:09:58 +0200, Eugeniu Patrascu said:

  We need an emergency fix because a piece of software unexpectedly hit
  an end-of-life date?  Didn't we learn anything 14 years ago??!?
 
 
 Juniper just posted a technical note saying the issue is fixed and a new
 ESAP package is out.

Right. The question is why it's coming out on the last day of December,
rather than the last day of November, or even October...


pgp29mBNo_SlB.pgp
Description: PGP signature


Re: Juniper SSL VPN

2013-12-31 Thread Matt Palmer
On Tue, Dec 31, 2013 at 04:19:24PM -0500, valdis.kletni...@vt.edu wrote:
 On Tue, 31 Dec 2013 23:09:58 +0200, Eugeniu Patrascu said:
 
   We need an emergency fix because a piece of software unexpectedly hit
   an end-of-life date?  Didn't we learn anything 14 years ago??!?
  
  
  Juniper just posted a technical note saying the issue is fixed and a new
  ESAP package is out.
 
 Right. The question is why it's coming out on the last day of December,
 rather than the last day of November, or even October...

To punish you for having the gall to think you could celebrate the new year
like a normal human being, instead of doing what you *should* be doing,
tending to the machines.

(At the risk of crossing the streams, I'll observe that I've not spent a new
year's eve or day patching my Linux-based VPN servers...)

- Matt

-- 
You keep using that word.  I do not think it means what you think it means.
-- Inigo, The Princess Bride




Re: Juniper SSL VPN

2013-12-31 Thread Eugeniu Patrascu
On Tue, Dec 31, 2013 at 11:19 PM, valdis.kletni...@vt.edu wrote:

 On Tue, 31 Dec 2013 23:09:58 +0200, Eugeniu Patrascu said:

   We need an emergency fix because a piece of software unexpectedly hit
   an end-of-life date?  Didn't we learn anything 14 years ago??!?
  
  
  Juniper just posted a technical note saying the issue is fixed and a new
  ESAP package is out.

 Right. The question is why it's coming out on the last day of December,
 rather than the last day of November, or even October...


From what I understood from the tech note, they had no clue this would
happen on the 31st of December :)


Re: Juniper SSL VPN

2013-12-31 Thread Christopher Morrow
Had no clue? Didn't they build it?
On Dec 31, 2013 7:46 PM, Eugeniu Patrascu eu...@imacandi.net wrote:

 On Tue, Dec 31, 2013 at 11:19 PM, valdis.kletni...@vt.edu wrote:

  On Tue, 31 Dec 2013 23:09:58 +0200, Eugeniu Patrascu said:
 
We need an emergency fix because a piece of software unexpectedly hit
an end-of-life date?  Didn't we learn anything 14 years ago??!?
   
   
   Juniper just posted a technical note saying the issue is fixed and a
 new
   ESAP package is out.
 
  Right. The question is why it's coming out on the last day of December,
  rather than the last day of November, or even October...
 

 From what I understood from the tech note, they had no clue this would
 happen on the 31st of December :)



Re: Juniper SSL VPN

2013-12-31 Thread Hank Nussbacher

At 20:55 31/12/2013 -0500, Christopher Morrow wrote:

Had no clue? Didn't they build it?

 From what I understood from the tech note, they had no clue this would
 happen on the 31st of December :)


Perhaps it is a left over somehow from their Netscreen purchase (April 2004)?

-Hank





Re: Juniper SSL VPN

2013-12-31 Thread Christopher Morrow
and in ~10 yrs no one did a code review? or refactor? or dependency check?

On Wed Jan 01 2014 at 12:42:09 AM, Hank Nussbacher h...@efes.iucc.ac.il
wrote:

 At 20:55 31/12/2013 -0500, Christopher Morrow wrote:
 Had no clue? Didn't they build it?
  
   From what I understood from the tech note, they had no clue this would
   happen on the 31st of December :)

 Perhaps it is a left over somehow from their Netscreen purchase (April
 2004)?

 -Hank