Hi Jon,

Where did you get your libgcrypt-1.4.4-5.el5 from. (Either a distro name or a URI would be helpful) and did you have to do an rpm rebuild before installing?

Faye

Jon Peatfield wrote:
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



--

---------------------------------------------------------
Faye Gibbins, Computing Officer (Infrastructure Services)
     GeoS KB; Linux, Unix, Security and Networks.
Beekeeper  - The Apiary Project, KB -   www.bees.ed.ac.uk
---------------------------------------------------------

  I grabbed at spannungsbogen before I knew I wanted it.
                 (x(x_(X_x(O_o)x_x)_X)x)
  Socrates: Question authority, question everything.
  If the maths works "Shut up and calculate!". Mermin.

The University of Edinburgh is a charitable body,
registered in Scotland, with registration number SC005336.

Reply via email to