Only problem with demanding this is that you /want/ people to be able to sell their car without access to a computer. That, and authentication.
Only problem with demanding this is that you /want/ people to be able to sell their car without access to a computer. That, and authentication.
I do understand that people are using these as a mental shorthand for "A one-way cryptographic hash", but when your instinctive exemplar of a digest algorithm is in the "not-recommended" category, it worries me that, in a context that matters (code or spec), you might accidentally type MD5 when you meant to type SHA3 or SHA-256
Or are there some more sophisticated methods?
E.g. How about in any binary content - embedded fonts, images etc.
My big concern is that in this scenario an attacker may have years to create an attack. One small part of designing a security protocol is understanding timeliness constraints.
Collision attacks are mitigated by careful examination coupled with a forbidding of extraneous data and a skepticism about possibly extraneous data - but I am not comfortable assuming they are defeated by it.