bug in smbmount and smbclient with 8bit filenames

Jason Haar Jason.Haar at trimble.co.nz
Sun Sep 10 23:05:12 GMT 2000


On Thu, Sep 07, 2000 at 10:37:41PM +0200, Urban Widmark wrote:
> On Wed, 6 Sep 2000, Jason Haar wrote:
> 
> > Looks wierder than that. That file actually contains a question-mark char -
> > which is (supposedly) illegal under Windows. I had our Windows guy do a
> > hexdump under Win2000, and it's 3F - "?"... which is the single-char
> > wildcard char.
> 
> Create a file a¨b.txt and list it with smbfs to repeat the problem.

OK,

touch a¨b.txt
/bin/ls a*.txt|hexdump 

0000000 a861 2e62 7874 0a74                    
0000008

cp a¨b.txt /path/to/smb/share/dir/
cd /path/to/smb/share/dir/
/bin/ls a*.txt|hexdump 

0000000 a861 2e62 7874 0a74                    
0000008


All looks fine.


> I think the bug is either that smbfs and smbclient do not tell the server
> clearly enough that they do not support unicode, or that the server does a
> bad translation for these non-unicode clients and then gets upset when the
> client responds with the translated string.

-- 
Cheers

Jason Haar

Unix/Network Specialist, Trimble NZ
Phone: +64 3 9635 377 Fax: +64 3 9635 417
               




More information about the samba mailing list