ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamv_5.4.0.1/rzamvifssecdirectory.htm

55 lines
3.3 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Secure directories" />
<meta name="abstract" content="To access an object within the root file system, you read through the entire path to that object." />
<meta name="description" content="To access an object within the root file system, you read through the entire path to that object." />
<meta name="DC.Relation" scheme="URI" content="rzamvplanifssec.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="ifssecdirectory" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Secure directories</title>
</head>
<body id="ifssecdirectory"><a name="ifssecdirectory"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Secure directories</h1>
<div><p>To access an object within the root file system, you read through
the entire path to that object.</p>
<p>To search a directory, you must have *X (*OBJOPR and *EXECUTE) authority
to that directory. Assume, for example, that you want to access the following
object: <span class="filepath">/companya/customers/custfile.dat</span> </p>
<p>You must have *X authority to the companya directory and to the customers
directory. </p>
<p>With the root file system, you can create a symbolic link to an object.
Conceptually, a symbolic link is an alias for a path name. Usually, it is
shorter and easier to remember than the full path name. A symbolic link does
not, however, create a different physical path to the object. The user still
needs *X authority to every directory and subdirectory in the physical path
to the object. </p>
<p>For objects in the root file system, you can use directory security just
as you might use library security in the QSYS.LIB file system. You can, for
example, set the public authority of a directory to *EXCLUDE to prevent public
users from accessing any objects within that tree.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvplanifssec.htm" title="The integrated file system provides you with multiple ways to store and view information on the server.">Plan integrated file system security</a></div>
</div>
</div>
</body>
</html>