Bug 42532 – Warn about or deny creation of nested file shares

Bug 42532 - Warn about or deny creation of nested file shares


Summary:	Warn about or deny creation of nested file shares

Status:	RESOLVED DUPLICATE of bug 44495

Product:	UCS
Classification:	Unclassified
Component:	UMC - Shares
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-09-29 11:39 CEST by Arvid Requate
Modified:	2017-07-13 16:33 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016092721000178
Bug group (optional):	Troubleshooting
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Arvid Requate

2016-09-29 11:39:48 CEST

We have had support cases where a customer reported problems for some users or user groups to access some files in some (Samba) file share.

In the cases I recall this was due to a lack of access permission to a parent directory for that user or group. In these cases this was caused by the customer who had configured a setup of nested (Samba) file shares, i.e. the customer created second share with a backing directory that was a subdirectory of another share (or the other way around).

IMHO it would be good to warn about (or deny, depending on UCR variable) the creation of nested (Samba) file shares.

Comment 1 Stefan Gohmann

2016-12-13 08:10:38 CET

The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.

Comment 2 Arvid Requate

2017-07-13 16:33:32 CEST


*** This bug has been marked as a duplicate of bug 44495 ***