JDK-7043737 : klist does not detect non-existing keytab
- Type: Bug
- Component: security-libs
- Sub-Component: org.ietf.jgss:krb5
- Affected Version: 7,7u1
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-05-11
- Updated: 2013-09-12
- Resolved: 2011-07-06
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.
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.
| JDK 7 | JDK 8 |
|---|---|
7u2Fixed  |
8 b01Fixed |
Description
Since "6894072: always refresh keytab", we support "dynamic" keytabs which means a keytab file can change during the execution of a program, this even includes accepting a non-existing keytab at the beginning and read it when it appears at a later time. On the other hand, the klist tool is used to list the current content of a static keytab file. When the file does not exist, we should warn the user. This behavior is also consistent with klist from other vendors.
Comments
|