<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Signature on ilham.dev</title><link>https://ilham.dev/tags/signature/</link><description>Recent content in Signature on ilham.dev</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0700</lastBuildDate><atom:link href="https://ilham.dev/tags/signature/index.xml" rel="self" type="application/rss+xml"/><item><title>How I check a PDF digital signature without confusing it with a drawn signature</title><link>https://ilham.dev/posts/how-to-check-digital-signatures-in-pdfs/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-check-digital-signatures-in-pdfs/</guid><description>A PDF digital signature is cryptographic metadata. It is not the same thing as an image of a handwritten signature placed on a page.
The PDF Signature Checker tool gives me a safe place to test the idea before I put it into a script, server, or production workflow.</description></item><item><title>How I understand SNAP BI asymmetric signatures step by step</title><link>https://ilham.dev/posts/how-to-understand-snap-bi-asymmetric-signature/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0700</pubDate><guid>https://ilham.dev/posts/how-to-understand-snap-bi-asymmetric-signature/</guid><description>SNAP BI signatures can feel confusing because they combine several ideas at once:
HTTP method; URL path; request body hash; timestamp; RSA private and public keys; a signature header. When all of those appear together, it is easy to get lost.</description></item></channel></rss>