we did, luckily i caught it early enough, found the solution (updating to java 1.4.2_03 in our case), and updated live servers before too many transactions got fucked.
would have been nice if Sun and/or Verisign has told anyone about this in advance.
sure they put out the java release a couple of weeks ago, but only with a miniscule release note:
bug #4924896 Ship currently published CA certificates in cacerts file."
it should have had a big fat warning like "UPGRADE NOW OR YOUR SITE WILL BREAK ON JAN 7th!"
i agree, if nothing else a lot of code that would otherwise never be seen is getting out there.
i find that being able to check out other commercial grade code, not the dumb little text-book style snippets but real apps/libraries, can be very educational when it comes to making higher level architectural decisions for my own projects.
Slashdot Mirror
we did, luckily i caught it early enough, found the solution (updating to java 1.4.2_03 in our case), and updated live servers before too many transactions got fucked.
would have been nice if Sun and/or Verisign has told anyone about this in advance.
sure they put out the java release a couple of weeks ago, but only with a miniscule release note:
bug #4924896
Ship currently published CA certificates in cacerts file."
it should have had a big fat warning like "UPGRADE NOW OR YOUR SITE WILL BREAK ON JAN 7th!"
bastards.
i find that being able to check out other commercial grade code, not the dumb little text-book style snippets but real apps/libraries, can be very educational when it comes to making higher level architectural decisions for my own projects.