符合 RSA PKCS#1 的签名
我正在使用 PKCS#1 2.0 (OAEP) 标准（带有附录的签名），但有一些问题我不清楚。
正在签名的物理对象是什么？我知道它的哈希函数值等等（我知道算法），但是它是从文件的二进制fform计算出来的，无论内容是什么？
签名的物理结果是什么？包含签名哈希的文件？该文件应该放置在指定位置吗？这种东西的格式或扩展是什么？
如果我想要签署多个文件，是否应该对每个文件单独执行此操作？还是应该将它们连接起来？再说一遍 - 这样的操作（文件？）的结果是什么？
I am using PKCS#1 2.0 (OAEP) standard (signature with appendix), but there are some issues not clear to me.
What is the physical object that is beeing signed? I know it's hash function value and so on (I do know the algorithm), but is it calculated from the binary fform of the file, no matter what is the content?
What is the physical result of signing? A file containing the signed hash? Should this file be placed in a specified location? What is the format or extension of such thing?
If I have several files that I want to sign, should this operation be performed separately for each of them? Or should they be concatenated? Once again - what is the result of such operation (file?) ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
PKCS#1 有时称为“原始 RSA”，是一种低级加密原语：它不适用于文件，也不生成文件，它适用于原始数据：输入是小于公钥和输出的数字是公钥大小的数字（例如，RSA-1024 为 1024 位）。
如果您想要签名文件，您可能需要使用PKCS#7/CMS格式，因为这是附加和分离签名最常用的签名格式（即使 PDF 文件中的签名实际上通常也是 PKCS#7 信封）。
PS：我对 OAEP 不太了解，但从我读到的内容来看，它似乎是一个填充方案（在原始签名之前对数据执行的操作），所以我的论点应该仍然有效。
PKCS#1 is sometimes called 'raw RSA' and is a low-level cryptographic primitive: it doesn't work on files and doesn't produce files, it works on raw data: input is a number smaller than the public key and output is a number of the size of the public key (e.g. 1024 bit for RSA-1024).
If you want a signature file, you probably want to use PKCS#7/CMS format, as that's the most used signature format both for attached and detached signatures (even signatures in PDF files are usually PKCS#7 envelopes actually).
PS: I don't know much about OAEP, but from what I read it seems to be a padding scheme (something you do to data before the raw signature) so my argument should be still valid.