Ted Unangst writes:
> On Mon, Dec 01, 2014 at 12:43, Dmitrij D. Czarkoff wrote:
> > Janne Johansson said:
> >> There is quite a bit of difference between changing the storage format and
> >> making some dates "impossible" that previously did work.
> > 
> > Don't think so.  Something got changed, things got broken and need to be
> > fixed.  The only real question is: is the change worth the trouble.  I
> > think it is, although unanimous negative reaction hints that I am
> > probably missing something important.
> > 
> 
> Fixing time_t did not suddenly make OpenBSD systems unable to
> communicate with other systems with other time_t sizes. It was an
> implementation detail, but the various protocols and formats that
> embed dates and times in them were not changed.
> 
> Your proposed change changes an important protocol: the one that lets
> me save files I receive from others to my filesystem. When I can no
> longer save web pages or email attachments and send them back to the
> sender with the same name, you have broken the protocol.

Should I be able to save web pages or email attachments with filenames
containing newlines?

How about backspaces?

What about terminal escape sequences, or ASCII control codes?

Yes, these have been possible in Unix since time immemorial. And the
fact that to this day there's no way for me to sanitize them terrifies me.

-- 
Anthony J. Bentley

Reply via email to