[19245] in Kerberos
Re: asn1 encoding for empty KDC_Options
daemon@ATHENA.MIT.EDU (Tom Yu)
Wed May 14 09:13:33 2003
To: "Naud, Eric" <eric.naud@Terayon.com>
From: Tom Yu <tlyu@MIT.EDU>
Date: Wed, 14 May 2003 09:12:42 -0400
In-Reply-To: <E54A98375651D511816A00306E06B970C8D8BA@OTNOAMEXCH01> ("Naud,
Eric"'s message of "Mon, 12 May 2003 10:51:36 -0700")
Message-ID: <ldvissdekol.fsf@cathode-dark-space.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
>>>>> "Eric" == Naud, Eric <eric.naud@Terayon.com> writes:
Eric> The KDC server and the ASN1 parser that I use both report an
Eric> error with the following bitstring encoding for the kdc options:
Eric> A0 07 03 05 00 00 00 00 00
Eric> It reports the following:
Eric> <A0 07>
Eric> . . . . [0] {
Eric> <03 05>
Eric> . . . . . BIT STRING 0 unused bits
Eric> . . . . . . '00000000000000000000000000000000'B
Eric> . . . . . . Error: Spurious zero bits in bitstring.
Eric> . . . . . }
Note that X.690 prohibits trailing zero bits in bitstrings, but only
for DER or CER, and even then only if NamedBits notation is used to
define the bitstring. Unfortunately, this is the case in RFC1510, so
pretty much all implementations of RFC1510 are not in compliance.
This is being fixed by changing the Kerberos specifcation within the
IETF to use bitstrings with unnamed bits. What implementations are
actually doing is emitting bitstrings of length 32 always.
Eric> Apparently ASN1 doesn't like null bit string, what should be
Eric> done in the case where the KDC-Options MUST NOT be set. Can I
Eric> just remove it from the aS request?
No. It is not an optional component of the AS-REQ. How are you
generating the AS-REQ? And which KDC implementation is giving you an
error on that bitstring? Which ASN.1 parser did you use to produce
the above trace?
---Tom
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
