On 06/12/2011 05:36 PM, Dominic Hargreaves wrote: > On Fri, May 13, 2011 at 07:38:41PM +0200, Dominique Dumont wrote: >> Le vendredi 13 mai 2011 00:31:52, Dominic Hargreaves a écrit : >>> This bug is caused by the fact that pperl names its socket files based >>> on the full path of the perl program being run under pperl, and there >>> is a fairly short limit on the full path of the socket (sun_path in >>> struct sockaddr_un from sys/un.h, 108 characters). The socket name is >>> being silently truncated on creation. >> >> How about hashing (à la MD5) the full path and use the result as the socket >> name ? See md5(3ssl) >> >> Although this would add a dependency on openssl... > > I agree that adding a dependency on openssl would not be ideal. This > doesn't have to be cryptographically secure, so would crypt(3) or > similar suffice? If the concerns around OpenSSL are licensing issues, there are many better-licensed message digest toolkits, including: * nettle * gcrypt * Digest::MD5 (or other modules within the Digest:: namespace). > Donations of code welcome at this point... Does this really need any extra code? --dkg
Attachment:
signature.asc
Description: OpenPGP digital signature