A friend recently asked me to decode some text he had received, which was in a mutant version of the base64 encoding. A quick search led me to the O'Reilly book /Unicode Explained/, which describes a "URL/file-system-safe variant" of base64 which uses '-' and '_' in place of the standard '+' and '/', respectively. We should not generate this nonstandard form, but we should accept it, since it is unambiguous, in accordance with Postel's Robustness Principle. (The specific reference is on page 308, found in Google Books for the search 'base64 with hyphen'.) Fix: I don't have a suggested fix (I hacked around it to answer the question at hand but the hack is not suitable for general use). I'm not sure if we should require a flag to be set (or a special version of b64_pton() to be called) to decode this version, or just treat it as normal base64.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
WIP patch: https://github.com/freebsd/freebsd-src/pull/970