We have received more security reports against #curl in 2026 so far than we did during the entire year back in 2024.

During the first three months we have received twice the amount of reports/week as we did last year.

Han kan ”släcka halva internet”: Vi måste skydda oss

För två år sedan var världen ett par klick ifrån digital undergång i en cyberattack.

Sydsvenskan
Sunday morning. Woke up to three fresh #curl security reports.

Guten Morgen! ☀️

Wusstet ihr, dass `curl` dieses Jahr 26 wird? Ein Tool das einfach... funktioniert. Kein Abo, kein "jetzt upgraden", kein dunkles Muster. Einfach HTTP-Request rein, Antwort raus, fertig.

Das ist die stille Magie von Open Source: Software die einfach ihren Job macht, ohne Drama. 🛠️

#OpenSource #Linux #curl #DevLife #FOSS

Meteorology

Current weather in Kwamalasemutu SR SA with the power of wttr.in & the grace of
lolcat(6) 🏳️‍🌈 wttr.in curl & {ba{c{k{z{fi}}}}}sh

Background photograph is a wolken dek {NL} composed in Commewijne SR SA

log

$ curl --verbose wttr.in/kwamalasemutu|lolcat
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0* Host wttr.in:80 was resolved.

  • IPv6: (none)
  • IPv4: 5.9.243.187
  • Trying 5.9.243.187:80...
  • connect to 5.9.243.187 port 80 from 10.2.2.137 port 36128 failed: Network is unreachable
  • Failed to connect to wttr.in port 80 after 5691 ms: Could not connect to server0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0
  • closing connection #0curl: (7) Failed to connect to wttr.in port 80 after 5691 ms: Could not connect to servermetalloid@krishna:~/gate/audio/raw/flac/αβeats∞$ curl --verbose wttr.in/kwamalasemutu|lolcat% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed0 0 0 0 0 0 0 0 --:--:-- 0:00:05 --:--:-- 0* Host wttr.in:80 was resolved.
  • IPv6: (none)
  • IPv4: 5.9.243.187
  • Trying 5.9.243.187:80...
  • Connected to wttr.in (5.9.243.187) port 80
  • using HTTP/1.x> GET /kwamalasemutu HTTP/1.1> Host: wttr.in> User-Agent: curl/8.14.1> Accept: />
  • Request completely sent off< HTTP/1.1 200 OK< Access-Control-Allow-Origin: *< Content-Length: 9194< Content-Type: text/plain; charset=utf-8< Date: Sun, 05 Apr 2026 01:51:54 GMT< { [2625 bytes data]100 9194 100 9194 0 0 1615 0 0:00:05 0:00:05 --:--:-- 1962
  • Connection #0 to host wttr.in left intactWeather report: kwamalasemutu

`/"".-. Patchy rain nearby
,_( ). +22(25) °C

/(() ↙ 5 km/h

‘ ‘ ‘ ‘ 10 km

‘ ‘ ‘ ‘ 0.0 mm

sources

https://wttr.in [API]

man bash(1)

man lolcat(6)

man xfce4-screenshooter(1)

man thunar(1)

Location: Kwamalasemutu, Coeroeni, Sipaliwini, Suriname [2.3554503,-56.787836]

Z

#Weather #wttr #lolcat #curl #bash #csk #ksh #zsh #sh #fish #meteorology #environment #Physics #Chemistry #Mathematics #Lineair #algebra #technology #OpenSource #programming #POSIX

#curl dns part III, the improvements in asynchronous DNS resolution.

https://eissing.org/icing/posts/curl-dns-async/

curl dns 2026, part III, async

In part I and part II I talked about the changes to DNS resolution in curl and why we do them. In this post I cover the difference and changes in synchronous vs asynchronous resolution. Which matter for Happy Eyeballs v3 (HEv3) and Encrypted Client Hellos (ECH). Sync/Async, Old and New Out of all the DNS options I described in part II, the most compatible and most deployed one is getaddrinfo(). Sync, no threads or c-ares

icing's blog
#curl 8.20.0-rc1 is here for your tests: https://curl.se/rc/
curl release candidates

« Pourquoi l'IA est à la fois une malédiction et une bénédiction pour les logiciels libres – selon les développeurs » - via la revue de presse @aprilorg

https://www.zdnet.fr/actualites/pourquoi-lia-est-a-la-fois-une-malediction-et-une-benediction-pour-les-logiciels-libres-selon-les-developpeurs-492500.htm

#opensource #GenAI #AI #enshitification #VieDeDev #cURL #Linux

Pourquoi l'IA est à la fois une malédiction et une bénédiction pour les logiciels libres – selon les développeurs - ZDNET

L'IA a transformé la sécurité du code, accaparant du temps, de l'attention et sapant le moral. Mais, bien utilisée, elle peut être utile. Voici comment.

ZDNET

The security reporting situation that I see at the ASF and in #curl is

- huge increase in reports
- increase of valid reports
- appearance of duplicate/triplicate reports of the same issue by different people

A high profile project needs to deal with 2-4 new reports each day. This is nuts.

One *may* hope this to go down again later this year bc
- unhallucinated issues are finite (see the fuzzing wave)
- eventually it will cost real money to generate these reports