[PATCH] Fix bug 10775 - smbd crashes when accessing garbage filenames

[Thomas Bork]

Am 28.08.2014 um 22:07 schrieb Jeremy Allison:

> Consider a directory exported by Samba with
> the default utf8 character set. An "evil" (tm:-)
> user with write access in the directory creates
> files within it with the non-utf8 sequences such
> as:
>
> \340|\231\216\377\177
>
> and
>
> \240\276\346\327\377\177

Will this also help with this?:

http://forum.nettworks.org/index.php?t=msg&th=5427&goto=32890&#msg_32890

The user copied files from an old server to an new server (dont know 
how) and messed up the encoding somehow.

Samba 4.1.11 cannot list the problematic files anymore (3.6.24 could, 
the user made an update of the samba package on the new server from 
internal 3.6.24 to 4.1.11).

smbclient stumbles over the files with other encoding and shows:
NT_STATUS_INFO_LENGTH_MISMATCH listing ...

-- 
der tom