At 00:22 2014-08-27, you wrote:
http://security.stackexchange.com/questions/17192/why-disallow-special-characters-in-a-password
On a related note, why disallow special characters in filenames?
Because Windows has some weird behaviour with some of
them. Some of it has been added over the years. Try these from a DOS window:
dir *^t
dir *^
I have no idea what carets do in a filename, and I do not care to
experiment to find out and to write special code to handle them. Nor
do I care to be surprised by other oddball characters. (Yes, I
understand that filenames as used in VFP may get different behaviour
than through a DOS windows. That only complicates the issue.)
Adobe Acrobat chokes on filenames containing some characters
that are ordinary to Windows. No, I did not save the list.
Between the two, rather than handle the whole mess, I
restricted client codes to having only A-Z, a-z, 0-9, periods, and
hyphens and filenames to having those and spaces. There have been no
complaints.
Pardon me. There was a complaint. After using Client Code
"***" for years as a suspense account, my boss finally wanted to
print a PDF under that account. Naturally, a filename with asterisks
in it does not work very well. The suspense Client Code is now
"---". This is when I implemented the restriction on characters.
I feel no remorse for my crimes as delineated above.
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
