# curl Published articles for curl. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Atomic macOS (AMOS) Stealer Activity DevFeed: [Atomic macOS (AMOS) Stealer Activity]() Original publisher: [Read original article]() Author: Bradley Duncan Published: 2026-09-16T10:00:06Z Content type: article Language: en Sources: [Unit 42]() Topics: [Malware](), [Aeternum](), [macOS](), [sensitive data](), [Zsh](), [ClickFix](), [cURL]() Tags: [ads](), [clickfix](), [credentials](), [cryptocurrency](), [curl](), [general](), [insights](), [macos](), [malware](), [sensitive-data](), [threat-intelligence](), [unit-42](), [zsh]() ### AI overview This article analyzes a laboratory-generated Atomic macOS (AMOS) stealer infection observed on Aug. 5, 2026. It describes a deceptive macOS toolkit installation page that led users to paste a command into Terminal, retrieving a Zsh script containing an encoded compressed payload and a follow-up script designed to run a Mach-O binary. AMOS targets macOS and can exfiltrate system information, login credentials, and sensitive data from applications including browsers and cryptocurrency wallets. ### Source excerpt Modern macOS malware uses deceptive setup guides to steal credentials and sensitive user data. Learn how to identify and block these threats. The post Atomic macOS (AMOS) Stealer Activity appeared first on Unit 42. ## Security updates for Monday DevFeed: [Security updates for Monday]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-14T13:18:14Z Content type: news Language: en Sources: [LWN.net]() Topics: [Security](), [Debian](), [Fedora](), [Firefox](), [Git](), [nginx](), [Python](), [cURL](), [Elixir](), [F#](), [Redis](), [Rust]() Tags: [curl](), [debian](), [elixir](), [firefox](), [git](), [nginx](), [python](), [redis](), [rust](), [security](), [updates]() ### AI overview Security updates were issued across AlmaLinux, Debian, Fedora, Gentoo, Mageia, Oracle, and SUSE. The affected software includes operating-system components, browsers, developer tools, programming-language packages, servers, libraries, and cloud-related utilities. ### Source excerpt Security updates have been issued by AlmaLinux (389-ds-base, apr-util, coreutils, freerdp, git-lfs, glib2, gstreamer1-plugins-base, kernel, libkcapi, nginx, nodejs:22, nodejs:24, osbuild-composer, perl-YAML-Syck, postgresql16-postgis, ruby, ruby4.0, ruby:3.3, and vim), Debian (jbig2dec, kamailio, nginx, spip, and xorg-server), Fedora (baresip, bind, bluez, bubblewrap, chirp, chromium, cockpit, composer, corosync, darktable, dokuwiki, elixir, exiv2, expat, firefox, freerdp, freerdp2, gdk-pixbuf2, gegl04, golang-x-perf, grpcurl, kernel, kernel-headers, libevent, libmongocrypt, libpcap, libre, libsoup3, memcached, mingw-expat, mingw-openexr, mongo-c-driver, mrtg, nagios-plugins, nsd, nss, openssl, openvpn, PackageKit, pdns-recursor, perl-Net-OAuth, perl-XML-Bare, php-pecl-mongodb2, python-asteval, python-pip, rclone, rest, rust-hickory-net, rust-hickory-proto, rust-hickory-resolver, rust-ppmd-rust, rust-webbrowser, srt, syncthing, tar, tkimg, and valkey), Gentoo (Chromium, Google Chrome, Microsoft Edge, Opera, Vivaldi and Ruby), Mageia (bind, ffmpeg, glibc, java-17-openjdk, java-21-openjdk, librabbitmq, perl-Catalyst-Plugin-Static-Simple, perl-Imager, tor, and xz), Oracle (389-ds:1.4, ansible-core, apr-util, coreutils, freerdp, git-lfs, glib2, gstreamer1-plugins-base, gzip, httpd:2.4, image-builder, java-21-openjdk, kernel, mrtg, nginx, osbuild-composer, perl-DBI, postgresql16-postgis, python-lxml, python3.12-lxml, redis:6, and vim), SUSE (389-ds, ansible-core, ansible-creator, azure-storage-azcopy, cargo-audit, chromedriver, chromium, clamav, containerized-data-importer1.65, containerized-data-importer1.66, curl, dracut, ffmpeg-4, google-guest-agent, google-osconfig-agent, helm, java-1_8_0-ibm, jupyter-nbconvert, kernel, libpng16, libusb-1_0, libvirt, multipath-tools, NetworkManager, opensc, openssl-3, perl-Authen-SASL, perl-HTML-FormHandler, perl-Mojolicious, perl-Protocol-HTTP2, python-jwcrypto, python-sqlparse, python-tornado6, python313-geopy, python313-modelscope ## The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI DevFeed: [The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-09-09T21:17:32Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [OpenAPI Specification](), [Documentation](), [REST API](), [Swagger](), [Testing](), [Postman](), [JavaScript](), [JSON](), [Authentication](), [cURL](), [Chrome](), [Open Source]() Tags: [api](), [api-documentation](), [authentication](), [chrome](), [chrome-extension](), [curl](), [documentation](), [github](), [javascript](), [json](), [openapi](), [pdf](), [postman](), [rest-api](), [swagger](), [testing]() ### AI overview The article reviews Tom Johnson's free "Documenting APIs: A guide for technical writers and engineers" course. It describes the course's 17 chapters, practical API-learning exercises, coverage of REST APIs, OpenAPI, Swagger UI, testing and publishing API documentation, and a PDF edition exceeding 900 pages. ### Source excerpt While researching information for my job about the Swagger UI and how it can be used for testing, I came across this free course, called Documenting APIs: A guide for technical writers and engineers at https://idratherbewriting.com/learnapidoc/docapis_overview.html written by Tom Johnson, a technical writer based in Seattle who works for Google. The course looks intense, containing 17 chapters talking about Introduction to REST APIs, using APIs like a developer, Documenting API endpoints, the Open API spec, Testing API docs, Publishing API docs, and more. From the Course Introduction: "You'll first learn about API documentation by using a simple weather API to put a weather forecast on your site. [...] As you use the API, you'll learn about endpoints, parameters, data types, authentication, curl, JSON, the command line, Chrome's Developer Console, JavaScript, and more. The idea is that rather than learning about these concepts independent of any context, you learn them by immersing yourself in a real scenario while using an API. Immersion in real scenarios makes these tools and technologies more meaningful. "We'll then transition into standards, tools, and specifications for REST APIs. You'll learn about the required sections in API documentation, analyze examples of REST API documentation from various companies, learn how to join an open-source project to get experience, and more. "[...] We'll also dive into specifications such as the OpenAPI specification and Swagger UI (which provides tooling for the OpenAPI specification). Additionally, you'll learn how to document native library APIs and generate Javadoc". Tom Johnson offers a PDF version of this free course... over 900 pages, with more always being added. It also offers many workshop-like activities you could put in an actual itinerary. You would need for the course: Chrome, since it provides "a Javascript Console that works well for inspecting JSON", the JSON Formatter Chrome extension, Postman, a GitHub acco ## One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice DevFeed: [One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-07T09:27:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [OpenAPI Specification](), [Model Context Protocol (MCP)](), [MCP Server](), [API](), [ASCII](), [HTTP](), [cURL]() Tags: [ai-gateway](), [ai-governance](), [ai-readiness](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [article](), [ascii](), [curl](), [developer](), [http](), [llm-governance](), [llm-observability](), [mcp-server](), [model-context-protocol](), [openapi]() ### AI overview This tutorial shows how to define an HTTP API once in an OpenAPI document and expose it through three surfaces: model-initiated tool calls, a REST endpoint accessed with curl, and an MCP server. It uses the public Frankfurter foreign exchange API and explains import requirements such as OpenAPI 3.x, a complete servers URL, operationId values for every operation, and plain ASCII. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given a genuinely satisfying assignment. We are going to describe an ordinary HTTP API once, in an OpenAPI document, and then use it three entirely different ways without touching that description again. A model will call it on its own initiative inside a chat. [...] The post One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice appeared first on Tyk API Management. ## curl 8.22.0 DevFeed: [curl 8.22.0]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-09-02T05:52:46Z Content type: release Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Security](), [HTTP](), [openssl](), [API](), [TLS (Transport Layer Security)](), [Command-line interface]() Tags: [bugfixes](), [command-line](), [curl](), [curl-and-libcurl](), [cve](), [cves](), [http](), [openssl](), [release](), [security](), [tls]() ### AI overview The curl 8.22.0 release includes six changes, 302 bug fixes, and nine curl/libcurl security fixes plus one wcurl fix. It adds Apple GSS Framework support, API guards, experimental HTTP Message Signatures support, and Apple fast UDP, while blocking NTLM fallback in SPNEGO and dropping TLS-SRP support. ### Source excerpt Welcome to this new release. Get it as always from https://curl.se. If you rather want a security-patched older release branch, stay tuned for the follow-up Rock-solid curl announcement within a few days. Release presentation Numbers the 276th release6 changes70 days (total: 10,887)302 bugfixes (total: 14,489)525 commits (total: 39,608)0 new public libcurl function (total: 100)4 new ... Continue reading curl 8.22.0 -> ## There's a libcurl.dll in my system32 DevFeed: [There's a libcurl.dll in my system32]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-08-17T21:27:36Z Content type: opinion Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Windows](), [Vulnerabilities](), [Library]() Tags: [curl](), [curl-and-libcurl](), [vulnerabilities](), [vulnerability-scanner](), [windows]() ### AI overview The article explains why a vulnerable libcurl.dll found in Windows System32 cannot safely be upgraded generically. Different Windows applications may install or build libcurl separately, so the application owner must identify and update the specific DLL. ### Source excerpt This afternoon I had a meeting with IT people at a huge US power infrastructure company. They had found a libcurl.dll file in their C:\Windows\System32 directory and asked us for help to upgrade it. Their vulnerability scanner identified it as vulnerable to several publicly known vulnerabilities. Can we bump it to the latest version please? ... Continue reading There's a libcurl.dll in my system32 -> ## curl performance DevFeed: [curl performance]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-08-14T11:20:32Z Content type: opinion Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Performance Testing](), [Development](), [Shell](), [Git]() Tags: [curl](), [curl-and-libcurl](), [git](), [performance](), [performance-testing](), [shell-script](), [testing]() ### AI overview This article describes an initial performance-testing effort for curl. It explains the difficulty of obtaining stable results on shared cloud infrastructure and outlines a local shell script that updates curl from git, builds it, runs tests, and records data and logs. ### Source excerpt tldr: the live version is here: https://curl.se/perf/ How fast is "fast" and is it good enough? Does it run as fast now as it did before or was there a regression? What exactly needs to be fast? How fast is it? These are questions that many projects and products face, and in curl we are ... Continue reading curl performance -> ## From a Large Allowlist to Three Denials: Permissions for a Coding Agent DevFeed: [From a Large Allowlist to Three Denials: Permissions for a Coding Agent]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-11T07:00:00Z Content type: opinion Language: en Sources: [Philipp Lehmann]() Topics: [coding](), [Bash](), [Linux](), [Authorization](), [Kernel](), [mount](), [Network](), [Command-line interface]() Tags: [agent](), [agents](), [coding](), [command-line](), [curl](), [kernel](), [linux](), [mount](), [network](), [permissions](), [sandboxing](), [security](), [shell]() ### AI overview The article argues that command allowlists are a poor security boundary for coding agents because the required command set continually expands and command names do not constrain effects. It proposes enforcing limits at the kernel level with Linux namespaces, a read-only root filesystem, scoped writable mounts, and dropped capabilities, allowing a shell to run while restricting its blast radius. ### Source excerpt bwrap --unshare-net --cap-drop ALL instead of a command allowlist: sandboxing a coding agent's shell so rm -rf and curl cannot leave the workspace. ## TIME serves bots a different website, and User-Agent is now a billing identity DevFeed: [TIME serves bots a different website, and User-Agent is now a billing identity]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T01:46:28Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [AI Bots](), [Bot](), [Crawler](), [SIEM, Security, Observability]() Tags: [ads](), [billing](), [bots](), [curl](), [logs](), [measurement](), [openai](), [routing]() ### AI overview The article examines how TIME serves different content to crawlers based on User-Agent headers and records bot reads as billable ad impressions. It argues that because clients can freely change the header, crawler identity is an unreliable basis for billing and measurement. ### Source excerpt TIME forks its content per crawler and logs each bot read as a billable ad impression. The routing key for that whole ledger is a header any client can type. ## Running Ollama Locally with Podman on Fedora Linux DevFeed: [Running Ollama Locally with Podman on Fedora Linux]() Original publisher: [Read original article]() Author: Yazan Monshed Published: 2026-08-05T08:00:00Z Content type: article Language: en Sources: [Fedora Magazine]() Topics: [Fedora](), [Large Language Model](), [Linux](), [Open Source Models & Datasets](), [API](), [cURL](), [GPU]() Tags: [ai-development](), [api](), [curl](), [fedora-project-community](), [gpu](), [large-language-models-llms](), [linux](), [llama](), [nvidia](), [offline](), [ollama](), [open-source](), [podman](), [privacy](), [python](), [terminal](), [using-software]() ### AI overview This article explains how to run Ollama locally in a Podman container on Fedora Linux. It covers installing or verifying Podman, creating persistent storage for model weights, running the Ollama container, downloading Llama 3, optionally enabling Nvidia GPU acceleration, and using Ollama's local REST API with curl. ### Source excerpt Running Large Language Models (LLMs) locally has become increasingly popular for development, privacy, and offline testing. Ollama makes this incredibly straightforward, allowing you to run models like Llama 3 or Mistral directly on your machine. By leveraging Podman on Fedora Linux, you can isolate Ollama inside a container. This approach keeps your host system clean [...] ## curl Maintainers Report on a Month-Long Pause in Vulnerability Reporting DevFeed: [curl Maintainers Report on a Month-Long Pause in Vulnerability Reporting]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-08-03T06:42:19Z Content type: opinion Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Maintainers](), [Open Source](), [Vulnerabilities]() Tags: [curl](), [curl-and-libcurl](), [maintainers](), [open-source](), [pull-requests](), [security](), [vulnerability]() ### AI overview curl maintainers describe the results of pausing vulnerability reporting for the month of July 2026. They report receiving no actionable vulnerability reports during the pause, feeling relief, and using the time to review pull requests, improve documentation, and recharge. ### Source excerpt At this exact moment curl's summer of bliss 2026 ends. We (the maintainers of curl) took the entire month of July off from vulnerability reporting and in this post I will try to explain how this went. (If you feel like skipping the wordy blab below, the single word answer is: fine) This was possibly ... Continue reading What the bliss taught us -> ## Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp) DevFeed: [Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp)]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-07-31T23:13:22Z Content type: article Language: en Sources: [Simon Willison]() Topics: [Model Context Protocol](), [Large Language Model](), [anthropic](), [HTTP](), [Command-line interface](), [JSON](), [Python](), [web applications]() Tags: [2026](), [agent](), [ai](), [ai-2-235](), [anthropic](), [anthropic-336](), [cli](), [codex](), [context](), [curl](), [datasette](), [datasette-1-542](), [generative-ai](), [generative-ai-1-981](), [http](), [json](), [llm](), [llm-631](), [llms](), [llms-1-947](), [mcp](), [mermaid](), [mermaid-5](), [model-context-protocol](), [model-context-protocol-35](), [projects](), [projects-553](), [shell](), [stateless](), [terminal]() ### AI overview This commentary examines the 2026-07-28 stateless Model Context Protocol specification. It argues that stateless MCP simplifies client and server implementation, improves auditability and control compared with shell-based agent access, and better supports scalable web applications by removing session state and session-affinity requirements. The article also introduces the mcp-explorer CLI tool and mentions datasette-mcp. ### Source excerpt Tuesday was Stateless MCP day - the rollout of MCP 2.0, or the 2026-07-28 Model Context Protocol specification to use the more formal but less memorable name. This is the most significant change to the MCP spec since it first launched, and has also served to reignite my personal interest in the protocol. For background: MCP is the Model Context Protocol, which describes a standard way to expose new tools to LLM-powered agent frameworks. It was introduced by Anthropic back in November 2024, had a huge spike of interest through much of 2025, and then became somewhat eclipsed by Skills (another Anthropic invention) when it became apparent that an agent harness with access to a terminal and curl could do most of what MCP did in a more flexible way. I wrote about that in my review of 2025. I'm coming back around to MCP now. Giving an agent a shell environment with the ability to access the internet is fraught with risk, and requires a strong model that is capable of effectively driving such an environment. MCP tools are easier to audit and control, and simple enough that smaller models that run on a laptop can still drive them reasonably well. The new stateless MCP specification also greatly decreases the complexity of implementing both clients and servers for the protocol. I built three of those this week! What's easier with stateless MCP The best demonstration of the difference between stateful and stateless MCP is in this May 21st blog post that introduced the RC for the new specification. It included a clear before-and-after example. The older stateful MCP (I'm going to call it "legacy MCP") required two HTTP requests - the first to initialize a session and obtain a Mcp-Session-Id, and the second to actually call the tool: POST /mcp HTTP/1.1 Content-Type: application/json { "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2025-11-25", "capabilities": { }, "clientInfo": { "name": "my-app", "version": "1.0" } } } POST /mcp HTTP/1.1 Mcp ## HTTP Message Signatures with curl DevFeed: [HTTP Message Signatures with curl]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-27T06:55:03Z Content type: release Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [HTTP](), [Authentication]() Tags: [curl](), [curl-and-libcurl](), [digital-signatures](), [ed25519](), [experimental](), [git](), [hmac](), [http](), [production](), [release]() ### AI overview curl experimentally supports HTTP Message Signatures based on RFC 9421, allowing users to sign selected HTTP request components with ed25519 or hmac-sha256 through new command-line and libcurl options. The feature must be explicitly enabled, is discouraged for production use, and is planned for curl 8.22.0. ### Source excerpt The recently published RFC 9421 describes how to do HTTP Message Signatures, and starting just now, curl experimentally supports them. Message Signatures The specification describes this as a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. It is a way to verify that selected parts ... Continue reading HTTP Message Signatures with curl -> ## 1,500 curl authors DevFeed: [1,500 curl authors]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-25T14:29:28Z Content type: opinion Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Git]() Tags: [curl](), [curl-and-libcurl](), [git]() ### AI overview The curl Git repository now includes contributions from 1,500 separate named individuals. The milestone follows the project surpassing 1,000 contributors four and a half years earlier, with Sameeh Jubran identified as the 1,500th author. ### Source excerpt It takes a village to make curl. A rather big village. I have not been a solo maintainer of curl for a long time and I don't even do half of the commits anymore Since today, the curl git repository holds the accumulated efforts from 1,500 separate and named individuals. Only 4.5 years since we ... Continue reading 1,500 curl authors -> ## Workshop Basel day three DevFeed: [Workshop Basel day three]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-16T20:01:14Z Content type: article Language: en Sources: [Daniel Stenberg]() Topics: [HTTP](), [Streaming](), [Latency](), [client](), [servers](), [browser]() Tags: [browser](), [curl](), [firefox](), [http](), [http-workshop](), [latency](), [network](), [proxy](), [request](), [series](), [server](), [streaming](), [uploads](), [web]() ### AI overview A report from the third day of an HTTP workshop covering Media over QUIC transport, reverse HTTP, and resumable uploads. It discusses MOQ's proposed lower complexity and latency, server-initiated HTTP requests through CDN proxies, and an HTTP upload-resumption draft using Location, HEAD, and PATCH. ### Source excerpt See also: day one, day two. There is only one thing that is better than two days of HTTP workshop, and that is of course three days of HTTP workshop. The final day of this edition of the series started out with us again shuffling around where we parked ourselves around the big table. Except ... Continue reading Workshop Basel day three -> ## How to submit effective vulnerability reports to open-source projects DevFeed: [How to submit effective vulnerability reports to open-source projects]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-06-29T07:47:43Z Content type: tutorial Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [vulnerability](), [Security](), [Maintainers](), [Open Source]() Tags: [curl](), [curl-and-libcurl](), [cve](), [guide](), [maintainers](), [open-source](), [security](), [vulnerability]() ### AI overview This guide explains how to submit effective vulnerability reports to open-source projects, drawing on curl maintainers' experience with more than one thousand reports. It emphasizes describing the real security impact, understanding the software's documented behavior and limitations, and making reports easy for maintainers to handle. ### Source excerpt Over the years, we have received, read and handled way over one thousand vulnerability reports filed against curl. We have seen most kinds. It is time for me to try to help future reporters by providing a short guide on how to submit a truly excellent vulnerability report to an Open Source project. Researchers We ... Continue reading Do excellent vulnerability reports -> ## Posting explains from tools (and not web browsers) DevFeed: [Posting explains from tools (and not web browsers)]() Original publisher: [Read original article]() Author: depesz Published: 2026-06-25T14:56:17Z Content type: tutorial Language: en Sources: [select \* from depesz;]() Topics: [cURL](), [Tool](), [Website]() Tags: [api](), [cli](), [curl](), [data](), [explain-depesz-com](), [json](), [tools](), [uncategorized]() ### AI overview This article explains how to post execution plans to explain.depesz.com using a tool such as curl and obtain JSON containing the information needed to extract a delete_key for later deletion. ### Source excerpt Some time ago (well, a month ago) someone called zam6ak reached to me and asked about extraction of delete_key from plans posted using tool, and not website. Specifically they were doing something like: curl --silent --include \ --request "POST" "https://explain.depesz.com/" \ --data-urlencode "title=sample" \ --data-urlencode "plan@sample-plan.txt" \ --data-urlencode "query@sample-query.sql" \ --data-urlencode "is_public=0" Which worked, and ... Continue reading "Posting explains from tools (and not web browsers)" ## Trace any Vercel request from the CLI DevFeed: [Trace any Vercel request from the CLI]() Original publisher: [Read original article]() Author: z0oks Published: 2026-06-03T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [OpenTelemetry](), [Traces](), [cURL]() Tags: [cli](), [curl](), [opentelemetry](), [terminal](), [traces](), [update](), [vercel]() ### AI overview Vercel CLI now supports generating OpenTelemetry Session Traces for requests and retrieving the resulting trace data by request ID. The feature is available on all plans. ### Source excerpt You can now generate Session Traces through the Vercel CLI. Use the new vercel curl --trace command to generate an OpenTelemetry trace to the specified endpoint from the terminal. Use the new vercel traces get command to fetch the generated trace by request ID. Available on all plans. Update the Vercel CLI to the latest version and run vercel curl --trace to get started. Learn more about the vercel curl CLI command. Read more ## Technology Short Take 196 DevFeed: [Technology Short Take 196]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2026-05-22T14:00:00Z Content type: article Language: en Sources: [Scott's Weblog]() Topics: [datacenter](), [networking](), [Cybersecurity](), [Linux](), [Terraform](), [Artificial Intelligence](), [Ansible](), [Large Language Model](), [Cloud](), [cURL](), [npm]() Tags: [ai](), [ansible](), [article](), [aws](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [curl](), [cybersecurity](), [data-center](), [devops](), [docker](), [go](), [iac](), [k8s](), [kubernetes](), [linux](), [llms](), [networking](), [npm](), [oci](), [security](), [technologies](), [terraform]() ### AI overview Technology Short Take 196 is a curated list of articles about data center technologies, covering networking, servers and hardware, security, cloud management, operating systems, and applications. Topics include Ansible and IPSet, WireGuard and Headscale, a compromised Bitwarden CLI package on NPM, curl vulnerabilities, Terraform, AWS MCP Server, AI-assisted infrastructure as code, llama.cpp on Apple Silicon, Chrome's local AI model installation, Linux 7.0 and PostgreSQL, and Linux desktop voice typing. ### Source excerpt Welcome to Technology Short Take 196! Just in time for the US Memorial Day holiday, I am back with another list of articles related to various data center technologies like networking, security, operating systems, and applications. You will find articles on VPNs, Linux local privilege escalation (LPE) vulnerabilities, browser quirks and workarounds, the death of Terraform (again), and so much more. Enjoy your weekend reading! Networking Andrew Ward shares an Ansible role to block abusive subnets using IPSet. From this article on switching to WireGuard from Tailscale, I learned about Headscale (an open source implementation of the Tailscale control plane). Servers/Hardware Doug Dawson looks at some innovations that continue to improve computing power. Doug's article includes a few items I hadn't yet heard of. Security Bitwarden confirmed a compromise of its CLI package on NPM. First, we had CopyFail. Now we have Dirty Frag and Fragnesia. Daniel Stenberg talks about how Mythos found a single vulnerability--yes, just one--in curl. I don't really have words for this...security incident? That doesn't seem like the correct way to describe such a massive oversight, especially when you realize it happened to a cybersecurity agency. "Oops" doesn't even begin to describe it. Cloud Computing/Cloud Management Graham Gilbert insists Terraform is dead. I wonder what sorts of things the AWS MCP Server will make possible? William Collins argues in favor of AI through IaC rather than instead of it. I enjoyed this article. Collins indicates that while authoring IaC using LLMs is working rather well, managing infrastructure using LLMs is another story entirely. If you're at all interested in the intersection of LLMs and IaC, I'd add this to your reading list. Operating Systems/Applications Eric Sloof looks at using llama.cpp to run your own local, private AI stack on Apple Silicon. Mat Duggan examines his descent from artist to mercenary as a result of finding LLMs more useful than he exp ## Why cURL is a practical debugger for HTTP problems DevFeed: [Why cURL is a practical debugger for HTTP problems]() Original publisher: [Read original article]() Author: fidelitas.io Published: 2026-05-17T08:15:00Z Content type: opinion Language: en Sources: [fidelitas.io]() Topics: [cURL](), [debug](), [Command-line interface](), [Unix]() Tags: [curl](), [debugging](), [headers](), [http](), [tooling](), [unix]() ### AI overview This opinionated developer article argues that cURL is especially useful for debugging HTTP problems in production and remote environments where graphical clients may be unavailable. It contrasts cURL's debugging role with GUI clients' strengths in exploration, sharing, onboarding, and code generation, and introduces commonly useful command-line flags. ### Source excerpt Postman is great. Insomnia is great. But the moment something goes wrong in production, the tool I reach for first is the one that's been on every Unix box since 1996. ## Use native curl syntax with Vercel CLI DevFeed: [Use native curl syntax with Vercel CLI]() Original publisher: [Read original article]() Author: Melkey Moksyakov Published: 2026-05-15T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [cURL](), [Deployment]() Tags: [cli](), [curl](), [deployment](), [documentation](), [update](), [vercel]() ### AI overview Vercel CLI now supports native curl syntax, including full URLs, bare hostnames, the --url flag, and paths for linked projects. ### Source excerpt You can now use native curl syntax with the Vercel CLI. The vercel curl command accepts full URLs, bare hostnames, and the --url flag, and uses your Vercel auth to bypass Deployment Protection. If you've linked a project, you can also pass just a path: Update to the latest Vercel CLI version and run vercel curl to get started. Learn more in the Vercel CLI documentation. Read more ## Securing a retail AI endpoint from abuse for virtual try on DevFeed: [Securing a retail AI endpoint from abuse for virtual try on]() Original publisher: [Read original article]() Author: Alexander Nohe Published: 2025-11-11T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Artificial Intelligence](), [Firebase](), [Authentication](), [Back end](), [Code](), [cURL]() Tags: [ai](), [app-check](), [attestation](), [authentication](), [backend](), [code](), [curl](), [devices](), [firebase](), [generation](), [genkit](), [how-to](), [image](), [model](), [rate-limiting](), [retail](), [server](), [token]() ### AI overview A tutorial on protecting a Firebase AI endpoint for a virtual try-on application. It explains using App Check, replay-protected tokens, authentication, and rate limiting to reduce unauthorized access, replayed requests, and excessive generation costs. ### Source excerpt Learn how to protect expensive AI features from abuse using Firebase App Check, Authentication, and rate limiting to ensure only legitimate users can access them. ## TLS Certificate Cheat Sheet - OpenSSL & Curl DevFeed: [TLS Certificate Cheat Sheet - OpenSSL & Curl]() Original publisher: [Read original article]() Author: Chris Hager Published: 2025-09-22T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [TLS (Transport Layer Security)](), [certificates](), [Cheat sheet](), [openssl](), [cURL]() Tags: [certificates](), [cheat-sheet](), [curl](), [openssl](), [tls](), [tools]() ### AI overview A cheat sheet for creating, inspecting, signing, validating, and testing TLS certificates and related keys and CSRs using OpenSSL and cURL. ### Source excerpt https://collective.flashbots.net/t/tls-certificates-know-how-quick-reference/5292 ## Docker Build and Run Platforms and Resolving exec /usr/bin/sh: exec format error DevFeed: [Docker Build and Run Platforms and Resolving exec /usr/bin/sh: exec format error]() Original publisher: [Read original article]() Author: Hiks Gerganov Published: 2025-09-06T06:29:25Z Content type: tutorial Language: en Sources: [Baeldung - Ops]() Topics: [Docker](), [Dockerfile](), [Docker Container](), [Docker Image](), [Containers](), [Debian](), [Bash](), [cURL]() Tags: [bash](), [configuration](), [curl](), [debian](), [docker](), [docker-container](), [docker-errors](), [errors](), [image](), [platforms]() ### AI overview This tutorial explains how Docker build and run platforms affect container compatibility. It demonstrates building and running a Docker image with a Dockerfile, specifying target platforms, and diagnosing exec format errors caused by mismatched architectures or other execution issues. ### Source excerpt Explore Docker build and run platforms, along with errors that they might lead to. Further, learn about alternative reasons for exec format error issues. Related Stories Troubleshooting the no configuration file provided: not found Error in Docker Compose What Is the Runtime Performance Cost of a Docker Container? Using a Package Manager in GitHub Actions [Next page]()