2010-02-25 07:24:00 +00:00
|
|
|
.\" Copyright (C) 2006 Red Hat, Inc. All Rights Reserved.
|
|
|
|
.\" Written by David Howells (dhowells@redhat.com)
|
|
|
|
.\"
|
2013-03-10 09:29:47 +00:00
|
|
|
.\" %%%LICENSE_START(GPLv2+_SW_ONEPARA)
|
2010-02-25 07:24:00 +00:00
|
|
|
.\" This program is free software; you can redistribute it and/or
|
|
|
|
.\" modify it under the terms of the GNU General Public License
|
|
|
|
.\" as published by the Free Software Foundation; either version
|
|
|
|
.\" 2 of the License, or (at your option) any later version.
|
2013-03-10 09:28:55 +00:00
|
|
|
.\" %%%LICENSE_END
|
2010-02-25 07:24:00 +00:00
|
|
|
.\"
|
add_key.2, keyctl.2, request_key.2, stime.2, time.2, ctime.3, difftime.3, ftime.3, getspnam.3, mq_receive.3, mq_send.3, rtime.3, sem_wait.3, string.3, timeradd.3, tzset.3, rtc.4, core.5, icmp.7, time.7, zic.8: Updated .TH timestamp
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2010-02-25 09:43:57 +00:00
|
|
|
.TH ADD_KEY 2 2010-02-25 Linux "Linux Key Management Calls"
|
2010-02-25 07:24:00 +00:00
|
|
|
.SH NAME
|
intro.1, add_key.2, get_mempolicy.2, get_thread_area.2, intro.2, keyctl.2, mbind.2, request_key.2, set_thread_area.2, clock.3, cmsg.3, getcwd.3, getpw.3, intro.3, malloc.3, posix_memalign.3, shm_open.3, sleep.3, sysconf.3, intro.4, sd.4, intro.5, locale.5, slabinfo.5, intro.6, boot.7, bootparam.7, futex.7, glob.7, hier.7, intro.7, libc.7, locale.7, mq_overview.7, netlink.7, sem_overview.7, shm_overview.7, unix.7, intro.8: Global fix: Use consistent capitalization in NAME section
The line(s) in the NAME section should only use capitals
where English usage dictates that. Otherwise, use
lowercase throughout.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2012-10-21 06:29:13 +00:00
|
|
|
add_key \- add a key to the kernel's key management facility
|
2010-02-25 07:24:00 +00:00
|
|
|
.SH SYNOPSIS
|
|
|
|
.nf
|
|
|
|
.B #include <keyutils.h>
|
|
|
|
.sp
|
|
|
|
.BI "key_serial_t add_key(const char *" type ", const char *" description ,
|
2011-11-07 02:43:14 +00:00
|
|
|
.BI " const void *" payload ", size_t " plen ,
|
|
|
|
.BI " key_serial_t " keyring ");"
|
add_key.2, keyctl.2, request_key.2, offsetof.3, pthread_attr_init.3, pthread_attr_setaffinity_np.3, pthread_attr_setdetachstate.3, pthread_attr_setguardsize.3, pthread_attr_setinheritsched.3, pthread_attr_setschedparam.3, pthread_attr_setschedpolicy.3, pthread_attr_setscope.3, pthread_attr_setstackaddr.3, pthread_attr_setstacksize.3, pthread_cancel.3, pthread_cleanup_push.3, pthread_cleanup_push_defer_np.3, pthread_equal.3, pthread_exit.3, pthread_getattr_np.3, pthread_getcpuclockid.3, pthread_self.3, pthread_setaffinity_np.3, pthread_setcancelstate.3, pthread_setconcurrency.3, pthread_setschedparam.3, pthread_setschedprio.3, pthread_testcancel.3: Global formatting fix: balance .nf/.fi pairs
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2012-03-12 15:37:22 +00:00
|
|
|
.fi
|
2010-02-25 07:24:00 +00:00
|
|
|
.SH DESCRIPTION
|
|
|
|
.BR add_key ()
|
|
|
|
asks the kernel to create or update a key of the given
|
|
|
|
.I type
|
|
|
|
and
|
|
|
|
.IR description ,
|
|
|
|
instantiate it with the
|
|
|
|
.I payload
|
|
|
|
of length
|
|
|
|
.IR plen ,
|
|
|
|
and to attach it to the nominated
|
|
|
|
.I keyring
|
|
|
|
and to return its serial number.
|
|
|
|
.P
|
|
|
|
The key type may reject the data if it's in the wrong format or in some other
|
|
|
|
way invalid.
|
|
|
|
.P
|
|
|
|
If the destination
|
|
|
|
.I keyring
|
|
|
|
already contains a key that matches the specified
|
|
|
|
.IR type " and " description
|
|
|
|
then, if the key type supports it, that key will be updated rather than a new
|
|
|
|
key being created; if not, a new key will be created and it will displace the
|
|
|
|
link to the extant key from the keyring.
|
|
|
|
.P
|
|
|
|
The destination
|
|
|
|
.I keyring
|
|
|
|
serial number may be that of a valid keyring to which the caller has write
|
|
|
|
permission, or it may be a special keyring ID:
|
|
|
|
.TP
|
|
|
|
.B KEY_SPEC_THREAD_KEYRING
|
|
|
|
This specifies the caller's thread-specific keyring.
|
|
|
|
.TP
|
|
|
|
.B KEY_SPEC_PROCESS_KEYRING
|
|
|
|
This specifies the caller's process-specific keyring.
|
|
|
|
.TP
|
|
|
|
.B KEY_SPEC_SESSION_KEYRING
|
|
|
|
This specifies the caller's session-specific keyring.
|
|
|
|
.TP
|
|
|
|
.B KEY_SPEC_USER_KEYRING
|
|
|
|
This specifies the caller's UID-specific keyring.
|
|
|
|
.TP
|
|
|
|
.B KEY_SPEC_USER_SESSION_KEYRING
|
|
|
|
This specifies the caller's UID-session keyring.
|
|
|
|
.SH KEY TYPES
|
|
|
|
There are a number of key types available in the core key management code, and
|
|
|
|
these can be specified to this function:
|
|
|
|
.TP
|
|
|
|
.B \*(lquser\*(rq
|
|
|
|
Keys of the user-defined key type may contain a blob of arbitrary data, and the
|
|
|
|
.I description
|
|
|
|
may be any valid string, though it is preferred that the description be
|
|
|
|
prefixed with a string representing the service to which the key is of interest
|
|
|
|
and a colon (for instance
|
|
|
|
.RB \*(lq afs:mykey \*(rq).
|
|
|
|
The
|
|
|
|
.I payload
|
2013-02-11 21:40:49 +00:00
|
|
|
may be empty or NULL for keys of this type.
|
2010-02-25 07:24:00 +00:00
|
|
|
.TP
|
|
|
|
.B \*(lqkeyring\*(rq
|
|
|
|
Keyrings are special key types that may contain links to sequences of other
|
2012-05-05 03:10:16 +00:00
|
|
|
keys of any type.
|
2013-02-11 21:40:49 +00:00
|
|
|
If this interface is used to create a keyring, then a NULL
|
2010-02-25 07:24:00 +00:00
|
|
|
.I payload
|
|
|
|
should be specified, and
|
|
|
|
.I plen
|
|
|
|
should be zero.
|
|
|
|
.SH RETURN VALUE
|
|
|
|
On success
|
|
|
|
.BR add_key ()
|
|
|
|
returns the serial number of the key it created or updated.
|
2013-02-11 21:40:49 +00:00
|
|
|
On error, the value \-1
|
2010-02-25 07:24:00 +00:00
|
|
|
will be returned and errno will have been set to an appropriate error.
|
|
|
|
.SH ERRORS
|
|
|
|
.TP
|
|
|
|
.B ENOKEY
|
|
|
|
The keyring doesn't exist.
|
|
|
|
.TP
|
|
|
|
.B EKEYEXPIRED
|
|
|
|
The keyring has expired.
|
|
|
|
.TP
|
|
|
|
.B EKEYREVOKED
|
|
|
|
The keyring has been revoked.
|
|
|
|
.TP
|
|
|
|
.B EINVAL
|
|
|
|
The payload data was invalid.
|
|
|
|
.TP
|
|
|
|
.B ENOMEM
|
|
|
|
Insufficient memory to create a key.
|
|
|
|
.TP
|
|
|
|
.B EDQUOT
|
|
|
|
The key quota for this user would be exceeded by creating this key or linking
|
|
|
|
it to the keyring.
|
|
|
|
.TP
|
|
|
|
.B EACCES
|
|
|
|
The keyring wasn't available for modification by the user.
|
|
|
|
.SH LINKING
|
|
|
|
Although this is a Linux system call, it is not present in
|
|
|
|
.I libc
|
|
|
|
but can be found rather in
|
|
|
|
.IR libkeyutils .
|
|
|
|
When linking,
|
|
|
|
.B -lkeyutils
|
|
|
|
should be specified to the linker.
|
|
|
|
.SH SEE ALSO
|
|
|
|
.BR keyctl (1),
|
|
|
|
.BR keyctl (2),
|
|
|
|
.BR request_key (2)
|