I\'m writing some code to digitally sign certain files (JSON, if you must know),

Question

I'm writing some code to digitally sign certain files (JSON, if you must know), and I'm trying to understand the use cases, not being a crypto guy myself.

I understand there are use cases where several parties all need to sign the same content, e.g. the two parties who enter a contract sign it to indicate their approval.

But are there use cases where B signs not just the content (of the contract, or whatever), but the concatenation of content plus the previously-created signature by A of the content?

Explanation / Answer

Maybe. Why not? Why would you rule this out? A signature is just bits. When you sign a message, you sign a stream of bits. If you are implementing a signature API, your API should allow a signer to sign any byte-sequence they like, and should allow them to get the signature as a byte-sequence. I can't imagine any reason why you would prohibit that. And if you allow that, the use case is already covered. So, I'm not clear why you are asking. What problem are you trying to solve? How will the answer to this question change how you design/implement your code?

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects