Pullup ticket #3575 - requested by obache
lang/sun-jdk6: security update
lang/sun-jre6: security update

Revisions pulled up:
- lang/sun-jdk6/Makefile                                        1.27
- lang/sun-jdk6/distinfo                                        1.16
- lang/sun-jre6/Makefile                                        1.33
- lang/sun-jre6/distinfo                                        1.19

---
  Module Name: pkgsrc
  Committed By: obache
  Date: Thu Oct 20 12:28:09 UTC 2011

  Modified Files:
  pkgsrc/lang/sun-jdk6: Makefile distinfo
  pkgsrc/lang/sun-jre6: Makefile distinfo

  Log Message:
  Update sun-{jdk,jre}6 to 6.0.29, aka, 6u29.

  Changes:

  [Olson Data 2011g]
  Java SE 6u29 contains Olson time zone data version 2011g. For more information,
  refer to Timezone Data Versions in the JRE Software .

  [Skipped Version Number]
  Release Java SE 6u29 follows release Java SE 6u27. There is no publicly
  available Java SE 6u28 release. Oracle used release version 6u28 for an internal
  build, which was not necessary once the fixes delivered on Java SE 6u29 were
  released.

  [Blacklist Entries]
  This update release includes the following new entries to the Blacklist:
    * Cisco AnyConnect Mobility Client
    * Microsoft UAG Client

  [RMI Registry Issue]
  A bug in the rmiregistry command included in this release may cause unintended
  exceptions to be thrown when an RMI server attempts to bind an exported object
  which includes codebase annotations using the "file:" URL scheme. The RMI
  servers most likely to be effected are those which are invoked only by RMI
  clients executing on the same host as the server.

  RMI annotates codebase information as part of the serialized state of a remote
  object reference to assist RMI clients in loading the required classes and
  interfaces associated with the object at runtime. Exported objects which are
  looked up in the RMI registry and invoked by RMI clients running on hosts other
  than the server are usually annotated with codebase URL schemes, such as
  "http:" or "ftp:" and these should continue to work correctly.

  As a workaround, RMI servers can set the java.rmi.server.codebase property to
  use codebase URLs other than the "file:" scheme for the objects they export.

  [Bug Fixes]
  This release contains fixes for security vulnerabilities. For more information,
  please see Oracle Java SE Critical Patch Update advisory.

(tron)