cram-md5 authentication does not work on AMD64 platform. Reproducible: Always Here is a super simple [PATCH] which fixes the problem and which should also work on every 32 bit architecture: ------------------------ SNIP ----------------------------------------------- Fix UINT4 type definition for AMD64. Will also work on 32 bit architecture. --- md5auth/global.h 2002-09-27 14:16:24.000000000 +0200 +++ md5auth/global.h 2008-10-26 16:04:38.000000000 +0100 @@ -17,7 +17,7 @@ typedef unsigned short int UINT2; /* UINT4 defines a four byte word */ -typedef unsigned long int UINT4; +typedef unsigned int UINT4; /* PROTO_LIST is defined depending on how PROTOTYPES is defined above. If using PROTOTYPES, then PROTO_LIST returns the list, otherwise it ------------------------ SNIP -----------------------------------------------
Created attachment 169938 [details, diff] Fixes UINT5 type definition, so it works for AMD64 platform. (Should also work for 32 bit platforms!) I think it would be a lot cleaner to use "u_int16_t" and "u_int32_t", but this would require to include "sys/types.h". Not sure if this is wanted.
Created attachment 169940 [details, diff] Fixes UINT4 type definition by using u_int32_t instead, This patch uses "u_int32_t" from "sys/types.h", but unfortunately this means a bigger patch. Choose which one you like
Did you report those patches upstream?
(In reply to comment #3) > Did you report those patches upstream? > Sorry for answering so late. It seems I did not get this via regular E-Mail. I didn't report this upstream. But now that you mentioned it I mailed the patch to 397149@bugs.debian.org and A.Monsalve.Salazar@IEEE.org (the Maintainer of ssmtp ?) I hope this helps ?
> ... > But now that you mentioned it I mailed the patch to > 397149@bugs.debian.org > and > A.Monsalve.Salazar@IEEE.org (the Maintainer of ssmtp ?) > > I hope this helps ? > Currently there seems to be no activity upstream. Would it be possible to just integrate this patch into gentoo ? so long Ingo PS: Just updated my system and again had to apply the patch myself...
I've also encountered this issue and would like to see the patch applied to the official ebuild.
This was fixed upstream for 2.64 so it's in tree now.