[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Updated: Security in Unicode
Pablo Saratxaga <pablo@xxxxxxxxxxxxxxxx>:
> > What if the software we are using would have built in sanity checks
> > using reversible algorithms to convert the bitstream to a view, and
> > convert it back to check if we get back the same stream? What
>
> I don't understand the usefulness of that.
It checks that no information is being thrown away by the viewing
software.
> Also, rendering is, by nature, always different: you change the width
> of your window and the text will wordwrap and linewrap at different places.
That is one of many things that makes it difficult to compute an
inverse of the viewing functions.
However, if you could use an inverse function for checking it would
catch many potential problems. For example, it might be that some
versions of the software show emphasised words in bold, but other
versions show nothing, because the font is missing, or something like
that, so a signed message in which the emphasised word "not" appears
at the end of a line could cause mischief as different recipients
interpret the message differently.
By the way, is this sort of problem more dangerous that I think it is?
I can't think of likely situations in which much damage would be done
by this sort of thing, and in any case there is always a potential
problem with different people interpreting the same message in
different ways while the communication is taking place in a "natural
language" like English or Basque or whatever. A clever writer can
deliberately exploit this.
Edmund
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/