JDK-8014196 : ktab creates a file with zero kt_vno
  • Type: Bug
  • Component: security-libs
  • Sub-Component: org.ietf.jgss:krb5
  • Affected Version: 7,8
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • Submitted: 2013-05-08
  • Updated: 2013-08-14
  • Resolved: 2013-05-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
7-poolResolved 8Resolved
When the ktab tool is used to add new entries, it would create a new file if there is no existing one. In order to find out if a file exists, we used to check if KeyTab.getInstance() is null. Since we support dynamic keytab, this method never returns null, and there is no chance to initialize kt_vno for an empty keytab file now.
verified as dup

I don't know how JBS works, but after I pushed the fix for 7u, it automatically creates a backport entry JDK-8015596 and this 8014196 is left untouched. So I just close it as a dup.

Max, why is this resolved as duplicate. Is the fix not integrated in jdk 8? 8015596 has fixversion of 7u40

Push to 7u-dev automatically generates 8015596.

Looked at code-review. Got clarifications from Max on queries INTJDK-7603737 opened for additional test on SQE side