Curl shipped with 14.1 has security issues and bugs!
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Curl shipped with 14.1 has security issues and bugs!
I've been battling a curl issue all morning, and updating to 7.35.0 fixes it. I would much rather use a stock slackware package so that I don't have slackpkg warning me to downgrade to the broken version in the repository.
Can someone update this and roll a security patch? It's just a matter of changing the version number and rebuilding the package.
I've been battling a curl issue all morning, and updating to 7.35.0 fixes it. I would much rather use a stock slackware package so that I don't have slackpkg warning me to downgrade to the broken version in the repository.
If you have already updated curl to 7.35 and your immediate objective is to eliminate slackpkg warning or prompt about curl, you may just add 'curl' to /etc/slackpkg/blacklist for the time being.
I've been battling a curl issue all morning, and updating to 7.35.0 fixes it. I would much rather use a stock slackware package so that I don't have slackpkg warning me to downgrade to the broken version in the repository.
Can someone update this and roll a security patch? It's just a matter of changing the version number and rebuilding the package.
Thanks,
schu
I used mancha's post as an opportunity to download the latest version of curl from its homepage, and compiled it myself. You can download the source here, and download the SlackBuild files that I have uploaded (gzipped tarball, just delete the '.txt' from the end of it).
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
This morning's [slackware-security] curl (SSA:2014-044-01):
Quote:
Here are the details from the Slackware 14.1 ChangeLog:
+--------------------------+
patches/packages/curl-7.35.0-i486-1_slack14.1.txz: Upgraded.
This update fixes a flaw where libcurl could, in some circumstances, reuse
the wrong connection when asked to do an NTLM-authenticated HTTP or HTTPS
request.
For more information, see: http://curl.haxx.se/docs/adv_20140129.html http://cve.mitre.org/cgi-bin/cvename...=CVE-2014-0015
(* Security fix *)
+--------------------------+
This is exactly what I was wanting. Sure I could build my own and blacklist the package in slackpkg (and did), but then I would need to pay attention to any future updates instead of relying on the Slackware user collective. This update fixes that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.