Anders Rundgren wrote:
I also understand your worries regarding what to sign and I would be very dishonest if I said I have "solved" it. In fact, my design doesn't even address this issue (!) except that if of course builds on the assumption that at least the "viewer" works as expected.
But it's the main issue! If you don't address this it's simply worth nothing. And you're bashing S/MIME use. Ah well...
You may be interested (still awake?) knowing that payment operations in brick-and-mortar shops is ultimately the most important application for the suggested scheme. Since this list doesn't really work with payments, I won't bore you to death with how this is supposed to work, but it does!
Real-world example: A company has many point-of-sale systems placed at external partner companies. Guess what? They have legal fights going on about real money. The question debated is whether the POS software itself worked correctly. Digital signatures wouldn't help in this situation since the partner would simply claim that what was displayed on screen was different from what was signed by the software. (They have a lab where each and every version of the software is installed for testing by assessors.)
Also when signing a contract by hand I usually get a physical copy of it which I can archive. That's not the case when doing web-signing. That's another important flaw of that scheme.
Ciao, Michael. _______________________________________________ dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
