Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why your PDF signature breaks the moment someone edits the file

A client sent me a signed supplier agreement last month with a note: "we changed one date in appendix 2, that's fine right?" The signature panel in their viewer still showed a green tick. In mine it said the signature was invalid. Both of us were looking at the same file. That disagreement is the whole problem with PDF signatures, and it is worth understanding before it happens to a contract you…

A client sent a signed supplier agreement with minor changes, yet the signature appeared invalid. This highlights the fundamental flaw in PDF signature verification - it only checks the file's bytes, not the document's actual content. When you sign a PDF, the tool signs specific byte ranges, not the meaning of the document. If those ranges shift due to edits, the signature becomes invalid.

PDFs support incremental updates, meaning adding comments or new signatures appends data to the end of the file while preserving the original byte ranges. This can lead to two outcomes: the signature remains technically valid but covers outdated content, or the signature becomes invalid entirely. To differentiate between these situations, use tools like pdfsig to check signature validity and coverage.

The most common scenario involves a signed contract being edited for minor changes, causing both the signature and its coverage to disappear. To avoid this, always re-sign the document if any changes occur after initial signing. Additionally, verify the signature's integrity before sending the file, and choose the appropriate type of signature based on regulatory requirements.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

ERC-2981 in practice: what a 5% royalty actually pays out

How an ERC-2981 royalty actually lands in a sale: in Seaport it is an extra consideration item with a fixed recipient, not a post-hoc transfer ERC-2981 does not transfer a royalty.

  • ERC-2981 royalty payout calculated via royaltyInfo function.
  • Seaport listing triggers royaltyInfo before signing order.
  • Seller net amount = price - royalty - marketplace fee.

Docker CI Jobs Need Cleanup Contracts

CI cleanup is usually treated as housekeeping. In a busy Docker pipeline, that is the wrong mental model. A container, temporary database, test inbox, or cloud runner left behind can change the next…

  • Docker CI jobs need structured cleanup approach
  • Assign unique run ID and owner to each resource
  • Implement external reaper for expired resources

More from Sunday 8 November →