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

krb5 shouldn't use an empty salt field in KRB_ERROR

XMLWordPrintable

        The salt field in the KRB-ERROR 25 (precisely, the salt in PA-ETYPE-INFO/2 as the edata field inside KRB-ERROR) is used by the server to suggest the correct salt. However, when connecting to a Windows Server with an encryption type the server does not support (like AES-128) it can be an empty string(""). When trying to renegotiate with the server, current Java code will use the empty string as the new salt and throws an Exception.

        When the user does not explicitly specify encryption type in krb5.conf and try to connect to a Windows Server, this bug always shows.

              weijun Weijun Wang
              weijun Weijun Wang
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: