Bug 139960
Summary: | Windows client can access unshared(!) server directory | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christian Ziemski <czml1> |
Component: | samba | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | jfeeney, mattdm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-31 04:37:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christian Ziemski
2004-11-18 22:24:11 UTC
The "rpm" share corresponds to the home directory of the "rpm" user, which is shared because your smb.conf file includes a section with the reserved name of "homes". The "homes" section includes default settings for home directory shares ("homes" is a reserved name for a share), and setting a path in that share will doubtless cause weird things to happen to shared home directories. But why isn't the "rpm" share visible initially, only after opening the context menu of "RPMS"? And why is it showing only after creating a share "RPMS"? I tested again: It does happen with other shares too which are named one character longer than an existing Linux user. (e.g. "ftp2", "root3"). There *is* happening something strange here! You wrote: "[path in homes share cause weird things]" That shouldn't happen! It's easy to have a not perfectly correct Samba configuration... It should be a bit more secure (defensive). Even with a correct configuration Samba shares too much in those cases, IMHO. I'll do more testing later today. Fedora Core 3 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 FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. |