Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4343409

getSOCKSReply version check limitation bug

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: P4 P4
    • None
    • 1.3.0
    • core-libs
    • generic
    • generic



      Name: skT45625 Date: 06/05/2000


      java version "1.2.2"
      Classic VM (build JDK-1.2.2-001, native threads, symcjit)

      java version "1.2.2.04"
      HotSpot VM (1.0.1fcs, mixed mode, PA1.1 build 1.2.2.04-00/04/14-PA_RISC1.1)

      Class file java/net/PlainSocketImpl.java on line 251 "requires" the returned
      version of the SOCKS server to equal "0". Here is a reply from an engineer at
      HP who wrote HP's SOCKS code:

      -Ah, you've discovered the problem that finally caused me to I give up
      -and changed the socks server... IIRC, the v3 protocol sent back '3'
      -as the first byte, and RFC1928 clearly makes v5 respond with '5' for the
      -first byte. The NEC (or was it Aventail) site documents the first byte
      -of the response to be '0' (apparently for a 'version 0 reply', or some
      -such thing.) The Java lib implements that, and is very strict in what
      -it will accept, violating good network programming practices.

      HP had to change their code to comply to the hard coded value in the JDK. I
      personally think you need a new check, or remove the current one, or give users
      the opportunity to set the value without having to change Operating System code
      that we have no access to.

      Mark Miller
      (Review ID: 105656)
      ======================================================================

            jccollet Jean-Christophe Collet (Inactive)
            skondamasunw Suresh Kondamareddy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: