Re: Blocking Windows Explorer from IFS shares

People commonly call the share the same name as the directory. For example
if you have a directory called /SecretStuff you may name the share
SecretStuff also. When you mark the directory hidden as with GUI
interfaces or with:
CHGATR OBJ('/SecretStuff') ATR(*HIDDEN) VALUE(*YES)
it doesn't make the share hidden, only the directory. So if you create a
share over this directory the share name doesn't generally stay hidden.
Hidden only applies to /SecretStuff not showing in the list with WRKLNK
'/*' or other related interfaces.
I've not played with the authorization list on a share to see if that hides
the share or not, or if it just stops it from showing.

An alternative might be to create a more obscure share and directory like
/Accounting27. Then secure the bejeezus out of that. Then the run of the
mill user, even if he can see a share named Accounting27 they cannot open
it and see any subdirectories underneath it like /Accounting27/SecretStuff.
I know that sometimes it's nice to hide stuff, even if it is secure, just
to avoid wetting their appetite to try harder to get to the data.

On Wed, Apr 26, 2023 at 11:26 AM Leandra MH Stewart <andie@xxxxxxxxxxxxxx>
wrote:

As anyone blocked a specific folder in the IFS from the windows explorer?

We have a folder with sensitive information that we want to block other
users from accessing. We have given access to 2 users, turned off
public access, told the share to be hidden, but the windows explorer can
still access the share.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.