T he kerberosv4 dissector is limited in functionality since
1, krb4 is hardly ever used any more at all (except you run some old
afs or dce/dfs site)
2, i dont have example captures of such packets.
Please send in example captures of missing krb4 packets if you want
them to be decoded.
I highly doubt the message "In prior
versions to 0.10.9, "BER: Choice field not found" appeared" appeared for krb4.
Kerberosv4 is NOT BER encoded and has never included or tried to
access any functions related to BER which makes this error
impossible for Krb4.
Maybe you are talking about kerberosv5? krb5 is what is used today and this
dissector is complete in ethereal,
ethereal can even, if you provide the propeer keytab file, decrypt
the kerberos packets for you to help troubleshooting authentication
issues.
And no, being able to dissect and decrypt kerberos5 is not a
security risk whatsoever.
On Tue, 22 Feb 2005 09:28:59 -0500, Pierre Goyette
<pierre@xxxxxxxxxxxxxxxx> wrote:
> I have some traces which contain UDP packets where a client requests a
> Kerberos V4 service ticket from a kdc and gets a response.
>
> Unfortunately, Ethereal cannot decode these packets at all. In prior
> versions to 0.10.9, "BER: Choice field not found" appeared. Now, nothing
> appears below "Kerberos" in the Packet Details window.
>
> Suggestions?
>
> Tia,
>
> Pierre
>
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
>