SCIENTIFIC-LINUX-USERS Archives

March 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jon Peatfield <[log in to unmask]>
Reply To:
Jon Peatfield <[log in to unmask]>
Date:
Mon, 29 Mar 2010 11:42:44 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (36 lines)
On Mon, 29 Mar 2010, Jon Peatfield wrote:

> On Mon, 29 Mar 2010, Faye Gibbins wrote:
>
>>  When trying to collect a https address, e.g:
>>
>>  lftp -c "get https://www.example.com/foo.tar.gz -o /tmp/foo.tar.gz"
>>
>>  lftp reports:
>>
>>  fgibbins$ lftp -c "get https://www.example.com/foo.tar.gz -o
>>  /tmp/foo.tar.gz"
>>  /usr/lib/libgnutls.so.13: symbol gcry_cipher_setkey, version GCRYPT_1.2
>>  not defined in file libgcrypt.so.11 with link time reference
>>  get: https - not supported protocol
>>  fgibbins$
>
> Once of our users reported the same problem this morning on our sl53 machines 
> - we did the gnutls security update on Saturday morning...
>
>>
>>  (Some domain names have been changed to protect the innocent)
>>
>>  Any thoughts on how to fix this?
>
> It appears that sl54 ships with a newer libgcrypt (1.4.4) so bindings to that 
> may have gotten into something that prevents it from working on earlier 
> versions of sl5x...
>
> I'm about to test pulling over the newer libgcrypt onto an sl53 box...

Just to confirm, updating to libgcrypt-1.4.4-5.el5 seems to fix it on both 
i386 and x86_64 machines...

  -- Jon

ATOM RSS1 RSS2