[ 
https://issues.apache.org/jira/browse/DIRKRB-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978455#comment-15978455
 ] 

Peter Cseh commented on DIRKRB-622:
-----------------------------------

I'll try to create a test early next week using a keytab that has this issue.
The difference in the codebase between directory-server's keytab reading 
mechanism is 
[here|https://github.com/apache/directory-server/blob/trunk/kerberos-codec/src/main/java/org/apache/directory/server/kerberos/shared/keytab/KeytabDecoder.java#L74].
It reads all the bytes defined by the entry size and it skips the bytes at the 
end if there are some what is not interpreted while Kerby reads and try to 
interpret all the bytes via an inputStream.

> Kerby does not skip empty parts of a keytab entry
> -------------------------------------------------
>
>                 Key: DIRKRB-622
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-622
>             Project: Directory Kerberos
>          Issue Type: Bug
>            Reporter: Peter Cseh
>
> The [keytab specifications 
> states|https://web.mit.edu/kerberos/krb5-devel/doc/formats/keytab_file_format.html]:
> {quote}
> A key entry may be smaller in size than the record length which precedes it, 
> because it may have replaced a hole which is larger than the key entry
> {quote}
> Kerby code does not comply to this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to