<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Rpm on Ashish Jaiswal</title>
    <link>https://ashish1099.me/tags/rpm/</link>
    <description>Recent content in Rpm on Ashish Jaiswal</description>
    <generator>Hugo -- 0.147.0</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 13 Mar 2026 09:00:00 +0530</lastBuildDate>
    <atom:link href="https://ashish1099.me/tags/rpm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Your RPM Host Showed 0 CVEs: Fixing Vuls Package Parsing in security-exporter</title>
      <link>https://ashish1099.me/posts/rpm-cve-detection-vuls2-security-exporter/</link>
      <pubDate>Fri, 13 Mar 2026 09:00:00 +0530</pubDate>
      <guid>https://ashish1099.me/posts/rpm-cve-detection-vuls2-security-exporter/</guid>
      <description>security-exporter returned 0 CVEs on every CentOS and RHEL host. The root cause was a silent data drop: ParsePackages silently skips any line that does not match its exact tab-separated format, and our rpm collector was producing the wrong format. This post covers the full diagnosis, the fix using the vuls-recommended 6-field rpm query, source package extraction using the NVR last-two-hyphens algorithm, and the Helm chart simplification that removed the entire legacy go-cve-dictionary + PostgreSQL pipeline.</description>
    </item>
  </channel>
</rss>
