71 lines
5.0 KiB
HTML
71 lines
5.0 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="reference" />
|
|
<meta name="DC.Title" content="Security" />
|
|
<meta name="abstract" content="When using the integrated file system APIs, you can restrict access to objects as you can when using data management interfaces. Be aware, however, that adopting authorities is not supported. An integrated file system API uses the authority of the user profile under which the job is running." />
|
|
<meta name="description" content="When using the integrated file system APIs, you can restrict access to objects as you can when using data management interfaces. Be aware, however, that adopting authorities is not supported. An integrated file system API uses the authority of the user profile under which the job is running." />
|
|
<meta name="DC.subject" content="integrated file system, programming interfaces, security, authority, handling in programs, access mode, mode of access, permission" />
|
|
<meta name="keywords" content="integrated file system, programming interfaces, security, authority, handling in programs, access mode, mode of access, permission" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxprogapi.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/chmod.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/fchmod.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/umask.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/unix2.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaaxapisec" />
|
|
<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>Security</title>
|
|
</head>
|
|
<body id="rzaaxapisec"><a name="rzaaxapisec"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Security</h1>
|
|
<div><p>When using the integrated file system APIs, you can restrict access
|
|
to objects as you can when using data management interfaces. Be aware, however,
|
|
that adopting authorities is not supported. An integrated file system API
|
|
uses the authority of the user profile under which the job is running.</p>
|
|
<div class="section"><p>Each file system may have its own special authority requirements.
|
|
NFS server jobs are the only exception to this rule. Network File System
|
|
server requests run under the profile of the user whose user identification
|
|
(UID) number was received by the NFS server at the time of the request.</p>
|
|
</div>
|
|
<div class="section"><p>Authorities on your server are the equivalent of <dfn class="term">permissions</dfn> on UNIX<sup>®</sup> systems.
|
|
The types of permissions are read and write (for a file or a directory) and
|
|
execute (for a file) or search (for a directory). The permissions are indicated
|
|
by a set of permission bits, which make up the <span class="q">"mode of access"</span> of the
|
|
file or directory. You can change the permission bits by using the <span class="q">"change
|
|
mode"</span> functions <span class="apiname">chmod()</span> or <span class="apiname">fchmod()</span>.
|
|
You can also use the <span class="apiname">umask()</span> function to control which
|
|
file permission bits are set each time a job creates a file.</p>
|
|
</div>
|
|
<div class="section"><p>For details on data security and authorities,
|
|
see the publication <a href="../books/sc415302.pdf" target="_blank">Security Reference</a> <img src="wbpdf.gif" alt="Link to PDF" />. </p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxprogapi.htm" title="Many of the application program interfaces (APIs) that perform operations on integrated file system objects are in the form of C language functions.">Perform operations using APIs</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../apis/chmod.htm">chmod() API</a></div>
|
|
<div><a href="../apis/fchmod.htm">fchmod() API</a></div>
|
|
<div><a href="../apis/umask.htm">umask() API</a></div>
|
|
<div><a href="../apis/unix2.htm">Integrated file system APIs</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |