Re: lib/rfc2617.c

From: Robert Collins <robert.collins@dont-contact.us>
Date: Wed, 7 Mar 2001 09:39:11 +1100

Yes thats the correct way to go... You'll get warning when you build
/src/auth/digest/auth_digest.c after making that change, (knock on
effect). So if you make that change, can you please build with digest
auth and track backwards?

Thanks,
Rob

----- Original Message -----
From: "Adrian Chadd" <adrian@creative.net.au>
To: <squid-dev@squid-cache.org>
Sent: Wednesday, March 07, 2001 9:26 AM
Subject: lib/rfc2617.c

>
> More cc fun. :)
>
> The mipspro cc compiler when using -fullwarn is spitting out
> the following:
>
> cc-1164 cc: WARNING File = rfc2617.c, Line = 108
> Argument of type "const char *" is incompatible with parameter of
type
> "const unsigned char *".
>
> MD5Update(&Md5Ctx, pszUserName, strlen(pszUserName));
> ^
>
> cc-1164 cc: WARNING File = rfc2617.c, Line = 110
> Argument of type "const char *" is incompatible with parameter of
type
> "const unsigned char *".
>
> MD5Update(&Md5Ctx, pszRealm, strlen(pszRealm));
> ^
> What should we do here? Convert the code to use unsigned char *
> when doing md5 stuff?
>
>
> Adrian
>
>
> --
> Adrian Chadd "The fact you can download a 100 megabyte file
> <adrian@creative.net.au> from half way around the world should be
viewed
> as an accident and not a right."
> -- Adrian Chadd and Bill Fumerola
>
Received on Tue Mar 06 2001 - 15:35:35 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:36 MST