Bug in CUI generation? Is this a known issue?

[Matthew Newton]

Hi,

On Fri, May 10, 2013 at 09:49:14AM +0000, stefan.paetow at diamond.ac.uk wrote:
> As you can see, the expand: bit shows an empty value. Then I
> changed my cui_hash_key to "01234567890abcdef01234567890abcdef"
> and it did the same. However, when I set cui_hash_key to a hex
> string that was not 32 characters in length ("abcdef" as an
> example), or a non-hex string of any length, it works ok. So I'm
> guessing here that if the cui_hash_key  happens to be a string
> that is a potentially valid MD5 hash, the md5 operator in the
> CUI generation statement does nothing or barfs.

Bug. src/main/xlat.c:1077 has:

   if (isdigit(l[1])) break;

which stops looking for a module_name (e.g. "md5" if the first
character after the : is a digit.

Fixed in 3.0 (see 4fd62ce9 22 August 2012).

Matthew


-- 
Matthew Newton, Ph.D. <mcn4 at le.ac.uk>

Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>