On 2021-04-29 18:24:30 -0700, Kevin J. McCarthy wrote: > Thanks Vincent. I'm reluctant to make changes to the sanitizer without > reports of issues.
Old MacOS versions seem to forbid ":" (colon): https://apple.stackexchange.com/questions/173529/when-did-the-colon-character-become-an-allowed-character-in-the-filesystem But see also https://stackoverflow.com/a/31976060/3782797 and the latest comments: On MacOS, the only forbidden printable ASCII character is :. Using the Windows superset of forbidden characters is sensible because it covers Linux and MacOS too. – AlainD Feb 10 at 12:27 I just confirmed @AlainD's comment. The only character I wasn't allowed to name my file is the colon character. However the reason for investigating was because I received a file from a windows user with a colon in it's name. – Dark Star1 Mar 3 at 11:41 > The Mutt code wraps the expandos in single quotes, and > launches it via /bin/sh. So, I'm not really clear about the purpose of the > sanitizer, unless it was to help protect against misuse by the mailcap > program invoked. There may be security issues with some programs. The following one is fixed, but there may still be similar ones around for programs written in Perl. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920269 -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
