1

Wikipedia's article on WYSIWYS is very brief, and says:

It is relatively easy to change the interpretation of a digital document by implementing changes on the computer system where the document is being processed

I didn't understand this. Can someone show an example? Thanks!

  • if i hacked your computer and replaced notepad with a clone that invisibly swaps true for false before saving but shows the un-replaced version, you wouldn't be signing what you thought you were when you process the file. – dandavis Aug 29 '19 at 17:00
3

The problem WYSIWYS is trying to prevent is that, when the same file is displayed with different software, or at a different time, or on a different system, etc, it may be displayed differently, even though the binary data is the same.

Imagine someone crafting a web page that displays differently in different browsers. If someone downloaded it as an HTML file and signed it, they would likely assume they had signed exactly the content they saw when they downloaded it, but another user who opens the HTML file in a different browser will see something completely different.

Another example is a document with external references (think images in a web page), even though the user is shown the image before signing the document, what they're really signing is a reference to that image. The user thinks they signed a document that includes the image, but the image being referenced could be modified without invalidating the signature.

| improve this answer | |
  • Ah, I see! Bonus question: is this even remotely solvable? – Pedro A Aug 29 '19 at 18:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.