Search

Items tagged with: curl


A real Hackerone #curl report title!:

"Out-of-bounds read in *** potential crash. This is sharp, <reporter name>. We've got a real memory safety bug"

The AI is helpfully cheering the guy onwards to slopping. Of course, it is a false positive.

#curl


In 2007 I did a talk about #curl at the FSCONS conference. The video is lost in time but today I realized that FSF Europe is still hosting the torrent file.

Not too many seeders of that content left though... 😎

download.fsfeurope.org/torrent…

#curl


#curl


#curl


I have already been asked how we intend to celebrate #curl's 30th anniversary next November (counted from httpget's birth)

But no, I have no idea. I'll think about that in about 11 months

#curl


Started a discussion about adding a timer notification to libcurl. If you use the "multi" interface, maybe you have an opinion?

#curl
github.com/curl/curl/
discussions/19553

#curl


#curl


#curl


if you are not happy on your FIPS system with modern #curl treatment of TLSv1.3, why not simply refrain from using curl?

Or take an older version and maintain it yourself.💁🏻‍♂️

github.com/curl/curl/pull/1934…

#curl



Should the default #curl progress meter use 1000-based units instead of 1024-based ones ?

  • 1000 (16%, 179 votes)
  • 1024 (83%, 904 votes)
1083 voters. Poll end: 1 week ago

#curl


Twenty-nine years ago on this day, #httpget 0.1 was released.

I found the tool a few days later and within a few months I became the maintainer. We later renamed it. Twice. The last name it got is #curl. It stuck.

httpget was my first insight and lesson into HTTP and since then I have kept learning it.

httpget 0.1 was written by Rafael Sagula, who unfortunately is not with us anymore.


six #curl security reports received within the last eight hours

I'm not getting the sense that things are improving.

#curl


#curl


one of the most common security reports we get in #curl is claims of various CRLF injections where a user injects a CRLF into their own command lines and that's apparently "an attack".

We have documented this risk if you pass in junk in curl options but that doesn't stop the reporters from reporting this to us. Over and over.

Here's a recent one.

hackerone.com/reports/3418616

#curl


In the #curl security team, we get to exercise deep protocol knowledge into the bits for many protocols including version variations and exploring funny quirks we have for adapting to many 3rd party libraries as well as a thorough understanding of the C language, how ABIs work, OS/platform variations and the occasional CPU peculiarity. Did I mention build systems?

And that's only for the issues we received this weekend.

#curl


You'd think merging on average eight bugfixes per day during the last #curl release cycle we would slow down a little now.

5 days after the release we are at:

Bugfixes logged: 48 (9.43 per day)

#curl


#curl



In #curl land, @vsz made a CI job that builds curl with fil-C and it runs the tests fine. Just slightly limited due to lack of dependencies as they all need to be built with fil-C as well.

github.com/curl/curl/pull/1939…

#curl @vsz


#curl


While on the topic of colorful #curl graphs. Complexity distribution in the source code over time. The recent effort to simplify code in curl has been done by multiple people through the last year or so. The graph's cyclomatic complexity is the score shown by the pmccabe tool.
#curl



More than half of #curl's source code lines have been changed within the last four years. 1,101 lines from before year 2000 still remain "untouched".
#curl


24 hours since a dot-zero #curl release with 400+ bugfixes and not a single annoying regression reported yet.

I'm not sure how to handle this.

#curl


1 open #curl issue for some Kerberos header file on IBM OS400 platforms…

I expected more from you…🦧

#curl


#curl



#curl


#curl


yes of course there is a graph of all #curl releases ever done. This includes the releases done using the previous names (httpget and urlget) as well
#curl


this is the 3rd #curl release ever done on November 5, as I trust you remember 7.19.0 and 7.39.0 back in 2008 and 2014
#curl


The #curl release on GitHub is now marked as "immutable" and there's even something they call "release attestation" there now.

Just remember that the curl canonical releases are the signed tarballs uploaded by me. Reproducible, so you can verify them at will to not contain bad things. Signed to prove I did them.

Made with love and care, I promise.

#curl


#curl


As per tradition, I will do a live-streamed #curl release presentation tomorrow 10:00 CET (my local time) over at twitch.tv/curlhacker
#curl


#curl