<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web-Services on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/web-services/</link>
    <description>Recent content in Web-Services on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 12 Nov 2026 10:03:35 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/web-services/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Beyond “Null Pointer” – A Pragmatic Guide to Detecting and Fixing Hidden Buffer Overflows in Rust‑Based Web Services</title>
      <link>https://linuxeries.org/post/2026-11-12-beyond-null-pointer-a-pragmatic-guide-to-dete/</link>
      <pubDate>Thu, 12 Nov 2026 10:03:35 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-12-beyond-null-pointer-a-pragmatic-guide-to-dete/</guid>
      <description>&lt;p&gt;Rust’s ownership model and type system give developers confidence that many classic memory bugs are impossible. Yet, when a web service talks to the outside world—HTTP payloads, database rows, or binary blobs—subtle buffer overflows can still surface. These bugs usually come from &lt;code&gt;unsafe&lt;/code&gt; blocks, FFI, or crates that expose raw pointers. In this post we dig into how such overflows arise in real‑world Rust services, show how to surface them with modern tooling, and outline practical mitigation steps that fit into a production pipeline.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
