Bug 4176 - lftp segfaults when listing files over https
Summary: lftp segfaults when listing files over https
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2012-01-17 23:03 CET by Thierry Vignaud
Modified: 2012-02-20 07:40 CET (History)
0 users

See Also:
Source RPM: lftp
CVE:
Status comment:


Attachments

Description Thierry Vignaud 2012-01-17 23:03:11 CET
lftp segfaults when listing files over https

$ gdb -q --args lftp https://fedorahosted.org/released/abrt/
(gdb) run
cd ok, cwd=/released/abrt                                               
lftp fedorahosted.org:/released/abrt> ls

Program received signal SIGSEGV, Segmentation fault.
lftp_ssl_gnutls::read (this=0x0, buf=0xa7d610 "", size=65536) at lftp_ssl.cc:541
541        if(error)
(gdb) bt
#0  lftp_ssl_gnutls::read (this=0x0, buf=0xa7d610 "", size=65536) at lftp_ssl.cc:541
#1  0x00007ffff3692f3f in IOBufferSSL::Get_LL (this=0xa63770, size=65536) at buffer_ssl.cc:84
#2  0x00007ffff3693044 in Do (this=0xa63770) at buffer_ssl.cc:56
#3  IOBufferSSL::Do (this=0xa63770) at buffer_ssl.cc:30
#4  0x0000003ce02297b6 in SMTask::Schedule () at SMTask.cc:237
#5  0x0000003cdf61ce7d in Job::WaitDone (this=0x61b3d0) at Job.cc:525
#6  0x0000000000406072 in main (argc=<optimized out>, argv=<optimized out>) at l
Comment 1 Manuel Hiebel 2012-01-18 04:29:32 CET
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => lists.jjorge

Comment 2 José Jorge 2012-02-19 22:18:29 CET
I could not reproduce on my i586 Cauldron. Is this bug still there in x86_64?
Comment 3 Thierry Vignaud 2012-02-20 07:40:38 CET
It got fixed with newer releases

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.