On Tue, Jul 5, 2011 at 6:20 PM, Hamza MIMI <inpt2...@gmail.com> wrote:
> *Hello all *
> *I am currently doing some tests using SIPp , and I noticed that the
> authentication header is truncated causing a registration failure!*
> *am doing an authentication with Digest / MD5 and the Opaque Value is
> always truncated in the same place ! *
> **
> *In the returned 401 : *
>
> Opaque Value: *
> "ALU:QbkRBthOEgEQAkhWV1hYRAIBHgkdHwQCQ1lFRkVWCQgucyo3JnZ0ZiAnOGI
> -KD1-PzcnbmBmbmg_"*
> **
> *In the following SIPp REGISTER (*opaque field is shortened*)*
>
>
>
> Opaque Value: *
> "ALU:QbkRBthOEgEQAkhWV1hYRAIBHgkdHwQCQ1lFRkVWCQgucyo3JnZ0ZiAnOGI"*
> **
> *
>
> according to RFC2617
>
>
>
> opaque
>
> A string of data, specified by the server, which should be returned
>
> by the client unchanged in the Authorization header of subsequent
>
> requests with URIs in the same protection space. It is recommended
>
> that this string be base64 or hexadecimal data.
>
> *
> **
> **
> **
> *I will apreciate any help regarding this issue *
>
> **
> *Thanks All*
>
*
*Looking at sipp code we see this:
char tmp[MAX_HEADER_LEN], authtype[16], cnonce[32], nc[32], *opaque[64];
*
So, opaque is too long and it is being truncated (63 chars plus
zero-terminator)
It should not be difficult do solve (assuming the issue is just this).
Do some tweaking (increase opaque buffer length) and recompile sipp.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
