*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->NetBSD man pages -> secure_path (3)              
Title
Content
Arch
Section
 

SECURE_PATH(3)

Contents


NAME    [Toc]    [Back]

     secure_path - determine if a file appears to be ``secure''

LIBRARY    [Toc]    [Back]

     System Utilities Library (libutil, -lutil)

SYNOPSIS    [Toc]    [Back]

     #include <util.h>

     int
     secure_path(const char *path);

DESCRIPTION    [Toc]    [Back]

     The secure_path() function takes a path name and returns zero if the referenced
 file is ``secure'', non-zero if not.  Any ``insecurity'', other
     than failure to access the referenced file, will be logged to the system
     log.

     To be ``secure'', the referenced file must exist, be a regular file (and
     not a directory), owned by the super-user, and writable only by the
     super-user.

SEE ALSO    [Toc]    [Back]

      
      
     openlog(3)

HISTORY    [Toc]    [Back]

     The secure_path function is based on the BSD/OS implementation of same,
     and appeared in NetBSD 1.5 by kind permission.

BSD                              July 16, 1996                             BSD
[ Back ]
 Similar pages
Name OS Title
_secure_path FreeBSD determine if a file appears to be secure
getwscrn IRIX returns the screen upon which the current window appears
rqsread IRIX reads the information out of an ELF file that is needed to determine if the file needs to be requickstarted
isastream Tru64 Determine if a file descriptor refers to a STREAMS file
sftp OpenBSD secure file transfer program
securettys Tru64 Secure terminal database file
sftp FreeBSD Secure file transfer program
ssh2_config Tru64 Configuration file for the Secure Shell client
sftp2 Tru64 Secure Shell file transfer client
sftp Tru64 Secure Shell file transfer client
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service