samba - Jan 2022 - unexpected name obfuscation

I suspect you've run across a reserved filename issue.

https://www.google.com/search?q=windows+reserved+filename

"From Microsoft's documentation: Do not use the following reserved
names for
the name of a file: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6,
COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9.
Also avoid these names followed immediately by an extension; for example,
NUL. "

It's a reserved filename; you won't be able to use it on windows ever,
at
least not without bugs and incompatibilities.

E.G. aux.something or any other long file name that gets stored as a segment
starting with AUX.
> -----Original Message-----
> From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Eric
> Levy via samba
> Sent: Sunday, January 09, 2022 9:18 AM
> To: samba at lists.samba.org
> Subject: [Samba] unexpected name obfuscation
> 
> Using Samba client I have mounted a share provided by a Samba server.
> Both endpoints are Linux Mint.
> 
> The shared folder sits on a Btrfs file system, and the top-level sub-
> directories have simple names. All are exposed directly but one, whose
> name is obfuscated. The actual name is not at all unusual, however,
> being only the three ASCII characters "aux".
> 
> The composition of the name may be easily verified, from a shell prompt
> on the server, as follows:
> 
> $ ls -1d aux | wc -c
> 4
> $ ls -1d aux | hexdump -c
> 0000000   a   u   x  \n
> 0000004
> 
> How may I expose the name without obfuscation?
> 
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

On Sun, 2022-01-09 at 21:48 -0800, Michael Evans via samba
wrote:
> I suspect you've run across a reserved filename issue.
> 
> https://www.google.com/search?q=windows+reserved+filename
> 
> "From Microsoft's documentation: Do not use the following reserved
> names for
> the name of a file: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5,
> COM6,
> COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and
> LPT9.
> Also avoid these names followed immediately by an extension; for
> example,
> NUL. "
> 
> It's a reserved filename; you won't be able to use it on windows
> ever, at
> least not without bugs and incompatibilities.
> 
> E.G. aux.something or any other long file name that gets stored as a
> segment
> starting with AUX.
I'm glad you have this information. I would never have guessed the
reason myself.

Does Samba provide any mechanism to override the behavior, if the
endpoints are all non-Windows?