Datasets:
memorylost731
/
linux_man_pages_library

Dataset card Data Studio Files Community
1
text
stringlengths
0
234
.ip
the arguments
.ir arg2 ,
.ir arg3 ,
.ir arg4 ,
and
.ir arg5
are ignored.
.ip
this operation is exposed by
.i libkeyutils
via the function
.br keyctl_session_to_parent (3).
.tp
.br keyctl_reject " (since linux 2.6.39)"
.\" commit fdd1b94581782a2ddf9124414e5b7a5f48ce2f9c
mark a key as negatively instantiated and set an expiration timer
on the key.
this operation provides a superset of the functionality of the earlier
.br keyctl_negate
operation.
.ip
the id of the key that is to be negatively instantiated is specified in
.i arg2
(cast to
.ir key_serial_t ).
the
.i arg3
(cast to
.ir "unsigned int" )
argument specifies the lifetime of the key, in seconds.
the
.i arg4
argument (cast to
.ir "unsigned int" )
specifies the error to be returned when a search hits this key;
typically, this is one of
.br ekeyrejected ,
.br ekeyrevoked ,
or
.br ekeyexpired .
.ip
if
.i arg5
(cast to
.ir key_serial_t )
is nonzero, then, subject to the same constraints and rules as
.br keyctl_link ,
the negatively instantiated key is linked into the keyring
whose id is specified in
.ir arg5 .
.ip
the caller must have the appropriate authorization key.
in other words, this operation is available only from a
.br request\-key (8)-style
program.
see
.br request_key (2).
.ip
the caller must have the appropriate authorization key,
and once the uninstantiated key has been instantiated,
the authorization key is revoked.
in other words, this operation is available only from a
.br request\-key (8)-style
program.
see
.br request_key (2)
for an explanation of uninstantiated keys and key instantiation.
.ip
this operation is exposed by
.i libkeyutils
via the function
.br keyctl_reject (3).
.tp
.br keyctl_instantiate_iov " (since linux 2.6.39)"
.\" commit ee009e4a0d4555ed522a631bae9896399674f063
instantiate an uninstantiated key with a payload specified
via a vector of buffers.
.ip
this operation is the same as
.br keyctl_instantiate ,
but the payload data is specified as an array of
.ir iovec
structures:
.ip
.in +4n
.ex
struct iovec {
void *iov_base; /* starting address of buffer */
size_t iov_len; /* size of buffer (in bytes) */
};
.ee
.in
.ip
the pointer to the payload vector is specified in
.ir arg3
(cast as
.ir "const struct iovec\ *" ).
the number of items in the vector is specified in
.ir arg4