[Asterisk-Dev] Authorization header not formatted properly when REGISTER msg is challenged (algorithm=MD5)

[Rob Gagnon]

OK, I agree.  So let's file the patch on bugs. and get it fixed.

I will look for it.  If it isnt there I will post it, and then copy this
chain with the Bug ID.  If someone else has already done so, please post the
link to the bug in this email chain.

Thanks.

Rob

----- Original Message ----- 
From: "Tilghman Lesher" <tilghman at mail.jeffandtilghman.com>
To: <asterisk-dev at lists.digium.com>
Sent: Thursday, July 22, 2004 11:26 PM
Subject: Re: [Asterisk-Dev] Authorization header not formatted properly when
REGISTER msg is challenged (algorithm=MD5)


> On Thursday 22 July 2004 17:47, Rob Gagnon wrote:
> > This is interesting....  You obviously are right, in that the
> > quotes fix your problem.  The issue seems to stem from an
> > inconsistency in RFC3261...
> >
> > Sections 20.27, and 20.44 show examples with the MD5 without
> > quotes: Example:
> >       Proxy-Authenticate: Digest realm="atlanta.com",
> >       domain="sip:ss1.carrier.com", qop="auth",
> >       nonce="f84f1cec41e6cbe5aea9c8e88d359",
> >       opaque="", stale=FALSE, algorithm=MD5
> >
> > Now, in Section 25.1 (Basic Rules), the value for "algorithm" is
> > shown to apparently require the quotes:
> >    algorithm = "algorithm" EQUAL ( "MD5" / "MD5-sess" / token )
>
> No inconsistency.  If the RFC writers had meant for the quotes to be
> there, they would have written:
>
> algorithm = "algorithm" EQUAL <"> ( "MD5" | "MD5-sess" | token ) <">
>
> Take a look at the stated grammar for one of the other fields that has
> quoted values, and you'll see the special notation.
>
> -- 
> Tilghman
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev