PDF的身份印章
我创建Ordius是为了解决一个我找不到清晰解决方案的问题：在保留PDF文档本身的情况下，为其建立一个确定性的身份标记。
Ordius为PDF创建一个ID，并将该身份嵌入文档中，以便后续验证。对我来说，重要的约束条件是Ordius不应规范化或重建文档，不修改其原始负载字节，不剥离元数据或维护元数据排除逻辑，不需要独立的身份文件，不依赖公钥基础设施（PKI），并保留提交的文档。
我喜欢认为这个构建解决了字节依赖悖论，结果是一个小型API，包含生成和验证操作。它的在线地址是：https://ordius.net/home/
我仍然有一些问题想要解答：云存储应用在上传和下载文档时是否保留Ordius块？当带有印章的PDF作为电子邮件附件发送时，Ordius块是否被保留？我测试过的情况是：在Gmail中发送带有Ordius印章的文档作为附件没有问题。
我希望听到与文档、PDF、签名、档案或文档完整性相关的人的反馈。我特别感兴趣的是有关方法中不必要摩擦的情况，以及在什么情况下这种方法不合适。
查看原文
I built Ordius to solve a problem I couldn't find a clean solution for: establishing a deterministic identity stamp for a PDF document while preserving the document itself.<p>Ordius creates an ID for a PDF and embeds that identity within the document so it can be verified later.
The important constraints for me were that Ordius should not normalize or reconstruct the document, modify its original payload bytes, strip metadata or maintain metadata exclusion logic, require a detached identity file, depend on PKI, and retain the submitted document.<p>I like to think the byte dependency paradox has been resolved by this build, and the result is a small API with Generate and Verify operations.
It's live here: https://ordius.net/home/<p>There are still some questions I am trying to answer: Do cloud storage applications preserve the Ordius Block when a document is uploaded and downloaded? Is the Ordius Block preserved when a stamped PDF is sent as an email attachment? What I have tested: sending an Ordius stamped document as an attachment in Gmail passes with no problems.<p>I'd like to hear from people who work with documents, PDFs, signing, archives, or document integrity. I'm particularly interested to hear about unnecessary friction in the approach and situations where it doesn't make sense.