#curl 8.13.0 has been released (#libcurl / #Haxx / #DICT / #FILE / #FTP / #FTPS / #Gopher / #HTTP / #HTTPS / #IMAP / #IMAPS / #LDAP / #LDAPS / #MQTT / #POP3 / #POP3S / #RTMP / #RTMPS / #RTSP / #SCP / #SFTP / #SMB / #SMBS / #SMTP / #SMTPS / #Telnet / #TFTP / #WebSocket / #SOCKS4 / #SOCKS5 / #SCRAM / #TLS / #HTTP2 / #HTTP3) https://curl.se/

Yesterday I requested a person to pay for support as they desperately asked me for immediate help with their #libcurl problem (for a huge international company doing an expensive commercial device), seemingly in a hurry.

To which the user said no thanks, closed the issue and vanished.

The open source life.

These days we celebrate twenty years since #git adopted #libcurl for their (HTTP) transfer needs

Two years ago we introduced the #libcurl header API, which also made it easier to extract headers with the #curl tool:

https://daniel.haxx.se/blog/2022/03/24/easier-header-picking-with-curl/

Tell us what you think of my latest proposal for how to improve redirect-following in #libcurl - in combination with custom methods.

https://github.com/curl/curl/pull/16473

Via another "crazy security scanner" report, I learn that #libcurl is installed in a #Microsoft Office and/or Teams install on Windows? According to the reddit post, in a normal install.

Does anyone know more?

The reddit page mentioning this: https://www.reddit.com/r/sysadmin/comments/1hx9eib/libcurl_vulnerability_in_office_and_teams/?sort=new

The libcurl mailing list post:

https://curl.se/mail/lib-2025-01/0086.html

Getting started with #libcurl
https://youtu.be/W-0yEqLMkwg

In ten minutes I will start the webinar "getting started with #libcurl". You can still join here: https://us02web.zoom.us/webinar/register/4216747720523/WN_2Yazx8c5THuav0P2JTc2Zw#/registration

Congratulations all crowd strike users on macOS who now get warnings about the #libcurl version shipped by Apple. May you all enjoy your choices of software vendors.

It alerts about CVE-2024-9681. We said it is severity low. NVD says 6.5 medium.

Never a dull moment.

The #libcurl backends image got a little less cluttered after we dropped hyper - no more HTTP/1 backends. The January 2025 edition.

Next week on Thursday Jan 9 comes a new chance to get to learn how to get started with #libcurl development in a live and free webinar with me. Sign up here:

https://us02web.zoom.us/webinar/register/4216747720523/WN_2Yazx8c5THuav0P2JTc2Zw#/registration

There's a Q&A too of course.

Integration of sandboxed-api for #libcurl?

https://github.com/curl/curl/discussions/15539

@bagder #curl (#libcurl, specifically) is used in Seat Leon (probably a VW-group thing); together with *a lot* of other #opensource (see the scrollbar).

Eleven years ago, the only long-lived #libcurl fork I am aware of was made: https://daniel.haxx.se/blog/2013/10/27/he-forked-off-libgnurl/

It existed for several years, but it seems to be completely gone now.

I bet you don't remember when #wget briefly considered switching to using #libcurl back in 2007.

https://daniel.haxx.se/blog/2007/10/27/wget-going-libcurl/

Can't seem to find configure flag to compile #libcurl without #ipfs support

While at it, here's a refreshed image of all #libcurl backends

my "advanced #libcurl" webinar runs tomorrow. Free of charge. Take the opportunity and ask me anything about (using) libcurl.

https://us02web.zoom.us/webinar/register/9316747720453/WN_zudyMou_RviqdgL-3QQXeg#/registration

#libcurl has proudly served as the HTTP(S) engine in #git for nineteen years now.