Adaptec 5325301507 Administration Guide - Page 112

Configuring Share and Folder Security Overview, Hidden Shares

Page 112 highlights

Configuring Share and Folder Security Overview Configuring Share and Folder Security Overview SnapServers support file access in Windows, UNIX, and Apple networks, as well as access via FTP and HTTP. Although the GuardianOS runs on an optimized Linux kernel and has many Linux characteristics, the cross-platform features make it very different than a pure Linux distribution. Systems running GuardianOS are storage appliances dedicated to file services. Administrators should not expect the same behavior as a pure Linux system when administering the SnapServer. By default, volumes are created with the Windows/Mixed security model (Windows-style ACLs for files created by SMB clients and UNIX-style permissions for files created by other protocols and processes), and allow all users to create, delete, and configure permissions on their own files and to access files and directories created by other users. New shares are created by default with full read-write access to all users, subject to the file system permissions on the share target directory. The first step to securing a SnapServer is to specify access at the individual share level. Administrators can assign Read/Write or Read-Only share access to individual Windows (and local) users and groups. Security permissions that have been applied to files and folders can be viewed from the Web View page of the Admin Tool. For users with admin rights, a key icon appears next to each file and folder in the share. Clicking this icon displays a popup box with security information about the file or folder. Hidden Shares There are three ways a share can be hidden in GuardianOS: • Name the share with a dollar-sign ($) at the end. This is the traditional Windows method of hiding shares; however, it does not truly hide the share since Windows clients themselves filter the shares from share lists. Other protocols can still see dollar-sign shares. • Hide the share from all protocols (except NFS) by navigating to Security > Shares > Create Share > Advanced Share Properties and selecting the Hide this Share check box, or by selecting a share, clicking to expand Advanced Share Properties, and selecting the Hide this Share check box. When a share is hidden this way, the share is invisible to clients, and must be explicitly specified to gain access. Note Hidden shares are not hidden from NFS, which cannot access invisible shares. To hide shares from NFS, consider disabling NFS access to the hidden shares. 96 SnapServer Administrator Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

Configuring Share and Folder Security Overview
96
SnapServer Administrator Guide
Configuring Share and Folder Security Overview
SnapServers support file access in Windows, UNIX, and Apple networks, as well as
access via FTP and HTTP. Although the GuardianOS runs on an optimized Linux
kernel and has many Linux characteristics, the cross-platform features make it very
different than a pure Linux distribution. Systems running GuardianOS are storage
appliances dedicated to file services. Administrators should not expect the same
behavior as a pure Linux system when administering the SnapServer.
By default, volumes are created with the Windows/Mixed security model
(Windows-style ACLs for files created by SMB clients and UNIX-style permissions
for files created by other protocols and processes), and allow all users to create,
delete, and configure permissions on their own files and to access files and
directories created by other users.
New shares are created by default with full read-write access to all users, subject to
the file system permissions on the share target directory. The first step to securing a
SnapServer is to specify access at the individual share level. Administrators can
assign Read/Write or Read-Only share access to individual Windows (and local)
users and groups.
Security permissions that have been applied to files and folders can be viewed from
the
Web View
page of the Admin Tool. For users with admin rights, a key icon
appears next to each file and folder in the share. Clicking this icon displays a popup
box with security information about the file or folder.
Hidden Shares
There are three ways a share can be hidden in GuardianOS:
Name the share with a dollar-sign ($) at the end. This is the traditional Windows
method of hiding shares; however, it does not truly hide the share since
Windows clients themselves filter the shares from share lists. Other protocols can
still see dollar-sign shares.
Hide the share from all protocols (except NFS) by navigating to
Security >
Shares > Create Share
> Advanced Share Properties
and selecting the
Hide this
Share
check box, or by selecting a share, clicking to expand
Advanced Share
Properties
, and selecting the
Hide this Share
check box.
When a share is hidden
this way, the share is invisible to clients, and must be explicitly specified to gain
access.
Note
Hidden shares are not hidden from NFS, which cannot access invisible
shares. To hide shares from NFS, consider disabling NFS access to the hidden
shares.