Bug 92165 - Trailing backslash in share description escapes newline in smb.conf
Summary: Trailing backslash in share description escapes newline in smb.conf
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-samba
Version: 9
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-03 15:04 UTC by Tom
Modified: 2007-04-18 16:54 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-07-03 21:47:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Tom 2003-06-03 15:04:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Would it be a good idea to prevent the entry of a backslash as the final
character in the Description field of the Create Samba Share dialog?

Version-Release number of selected component (if applicable):
redhat-config-samba-1.0.4-1

How reproducible:
Always

Steps to Reproduce:
1. Launch Samba Server Configuration utility
2. Click Add to create a new share
3. Type a backslash as the last character in the description field.
    

Actual Results:  The backslash escapes the newline character in the smb.conf
file causing the content of the following line (probably path=...) to display in
the description field on Windows Explorer.  The absence of the path=... line
then casuses Samba to search through the file for the next similar statement
which will likely be in the following share section.  This means it is possible
to inadvertantly apply undesired access policies.

Expected Results:  The GUI should either prevent entry of a backslash as the
final character or escape such a backslash so that it appears in the description
as the user intended.

Additional info:

Comment 1 Brent Fox 2003-07-03 21:47:51 UTC
Should be fixed in redhat-config-samba-1.0.8-1 in Rawhide.  Thanks for your report.


Note You need to log in before you can comment on or make changes to this bug.