From: Stephan Mueller <stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: 'Herbert Xu' <herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org>
Subject: [PATCH] socket.2: document AF_ALG
Date: Thu, 29 Jan 2015 17:29:34 +0100 [thread overview]
Message-ID: <2022953.c9E5IKVA29@tauon> (raw)
Add a reference to the AF_ALG protocol accessible via socket(2).
Signed-off-by: Stephan Mueller <stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
CC: Herbert Xu <herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org>
---
man2/socket.2 | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/man2/socket.2 b/man2/socket.2
index 229dab3..8885079 100644
--- a/man2/socket.2
+++ b/man2/socket.2
@@ -116,6 +116,11 @@ Low level packet interface
T}:T{
.BR packet (7)
T}
+T{
+.B AF_ALG
+T}:T{
+Interface to kernel crypto API
+T}
.TE
.PP
The socket has the indicated
@@ -378,6 +383,12 @@ families.
However, already the BSD man page promises: "The protocol
family generally is the same as the address family", and subsequent
standards use AF_* everywhere.
+
+The AF_ALG protocol type is added with kernel version 2.6.38. More
+information on this interface is provided with
+Documentation/crypto/crypto-API-userspace.txt provided in the
+Linux kernel source code tree.
+
.SH EXAMPLE
An example of the use of
.BR socket ()
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-01-29 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 16:29 Stephan Mueller [this message]
2015-01-30 6:05 ` [PATCH] socket.2: document AF_ALG Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2022953.c9E5IKVA29@tauon \
--to=stephan.mueller-fwyzokdejagavxtiumwx3w@public.gmane.org \
--cc=herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.