HP-UX Reference (11i v2 04/09) - 3 Library Functions N-Z (vol 7)

s
secure_rpc(3N) secure_rpc(3N)
and a DES key deskey, and encrypts it using the public key of the the server and the secret key
associated with the effective UID of the calling process. It is the inverse of
key_decryptsession()
. This routine returns 0
if it succeeds, -1 if it fails.
int key_gendes()
key_gendes() is a keyserver interface routine. It is used to ask the keyserver for a secure
conversation key. Choosing one at random is usually not good enough, because the common ways of
choosing random numbers, such as using the current time, are very easy to guess. This routine
returns 0 if it succeeds, -1
if it fails.
int key_setsecret()
key_setsecret()
is a keyserver interface routine. It is used to set the key for the effective UID
of the calling process. This routine returns
0 if it succeeds, -1 if it fails.
int key_secretkey_is_set(void)
key_secretkey_is_set()
is a keyserver interface routine that may be used to determine
whether a key has been set for the effective UID of the calling process. If the keyserver has a key
stored for the effective UID of the calling process, this routine returns
1. Otherwise it returns 0.
int netname2host()
Convert from an operating system independent netname name to a domain-specific hostname host.
hostlen is the maximum size of host. Returns
1 if it succeeds, and 0 if it fails. Inverse of
host2netname().
int netname2user()
Convert from an operating system independent netname to a domain-specific user ID. Returns 1
if
it succeeds, and
0 if it fails. Inverse of user2netname()
.
*uidp is set to the user’s numerical ID associated with name.
*gidp is set to the numerical ID of the
user’s group. gidlist contains the numerical IDs of the other groups to which the user belongs.
*gidlenp is set to the number of valid group ID entries in gidlist .
int user2netname()
Convert from a domain-specific username to an operating system independent netname. Returns 1
if it succeeds, and 0 if it fails. Inverse of netname2user()
.
MULTITHREAD USAGE
Thread Safe: Yes
Cancel Safe: Yes
Fork Safe: No
Async-cancel Safe: No
Async-signal Safe: No
These functions can be called safely in a multithreaded environment. They may be cancellation points in
that they call functions that are cancel points.
In a multithreaded environment, these functions are not safe to be called by a child process after
fork()
and before exec(). These functions should not be called by a multithreaded application that support
asynchronous cancellation or asynchronous signals.
SEE ALSO
chkey(1), keyserv(1M), newkey(1M), rpc(3N), rpc_clnt_auth(3N).
HP-UX 11i Version 2: September 2004 3 Hewlett-Packard Company Section 3953