Jeremy Allison
2021-Jan-02 23:29 UTC
[Samba] libsmbclient support for ? < > \ : * | " characters possible?
On Sat, Jan 02, 2021 at 03:10:59PM -0500, Andrew Walker via samba wrote:> >I suppose doing something like MacOS (and Samba with VFS fruit with >"fruit:encoding=native") would be maybe useful. In this case, the server >and client both sort of agree on how illegal characters will go over the >wire. A concrete example: 0x3a (colon) gets mapped to 0xf022 when it gets >sent over the wire, then the server converts said character back to 0x3a. >But of course, this is not sending the illegal character to the SMB server.This is a possibility. Could be done with existing Samba via a name-mapping VFS module (look at the catia and existing ones for an example).
Andrew Walker
2021-Jan-03 01:01 UTC
[Samba] libsmbclient support for ? < > \ : * | " characters possible?
On Sat, Jan 2, 2021 at 6:29 PM Jeremy Allison <jra at samba.org> wrote:> On Sat, Jan 02, 2021 at 03:10:59PM -0500, Andrew Walker via samba wrote: > > > >I suppose doing something like MacOS (and Samba with VFS fruit with > >"fruit:encoding=native") would be maybe useful. In this case, the server > >and client both sort of agree on how illegal characters will go over the > >wire. A concrete example: 0x3a (colon) gets mapped to 0xf022 when it gets > >sent over the wire, then the server converts said character back to 0x3a. > >But of course, this is not sending the illegal character to the SMB > server. > > This is a possibility. Could be done with existing Samba > via a name-mapping VFS module (look at the catia and > existing ones for an example). >Indeed. The maps themselves are rather annoying to figure out. It would be nice if there was a simple config option for catia like "catia:sfm = true" to just apply the giant messy block of mappings needed for the correct behavior without vfs_fruit (I suppose I should probably just make a merge request for this and discuss there).