Red Hat Bugzilla – Bug 132305
incorrect name hashes
Last modified: 2007-11-30 17:10:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2)
Description of problem:
When a directory name ends with a dot (.), samba expose the wrong name
For example: on my server the directory 'q.' is exposed as 'QVFH17~8'
when I look at is from an XP system.
This server has no 'special' settings changed that would influence
this behaviour in any obvious way
Just tested with regular files: same behaviour :-(
file 'qq.' is exposed as 'QYN4UX~R'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. make a directory q.
2. make a file qq.
3. look at the samba share with a win xp system and see the behaviour
Created attachment 103701 [details]
Screenshot of described bug
also did a local smbmount on the server of the share and same
behaviour, even looking at it from the server itself. so we can safely
assume it's not the fault of the xp system (this time).
trying to access the 'q.' directory by its 'q.' name does not work,
can only access it with the wrong name hash
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
I just checked it on a fresh FC4 Test 3 system, no change, same problem.
I'll upload two screenshots.
The share on the FC4t3 server has two items: a directory that is named
'dir_end_dot.' and a file that is named 'file_end_dot.'
The first screenshot is looking at the share from a Windows XP Home workstation,
the second screenshot is looking at the share from the FC4t3 server itself.
Created attachment 115147 [details]
Windows XP looking at the FC4t3 share
Created attachment 115148 [details]
FC4t3 looking at the FC4t3 share
just did a test on a FC6 server, problem persists!
This is not a bug.
Windows clients can't understand names the terminate with a ., so samba mangles
the name in a 8.3 format (wihtout the extension as the original file does not
have it in this case).