Menu

#32 issues with AD kerberos

open
nobody
None
5
2012-11-20
2012-03-22
Anonymous
No

When AD generated ticket, the kerberos blob size could be very big. Currently in xdr_rpc_gss_init_args,
RPC_SLACK_SPACE (1024) is passed to xdr_bytes as the maxsize and will fail with ticket generated by AD/KDC.
We see this problem with a nfs server which uses tirpc to handle rpcsec with kerberos configured with AD.

1024 is for sure very small, though I am not sure why it cannot use (u_int)-1 ? Is this to avoid rouge PDU?

Discussion