From 4a7535aa8ed90a598d8a932adc61fe6009ebbd01 Mon Sep 17 00:00:00 2001 From: Andre Noll Date: Sun, 6 Sep 2015 21:55:13 +0200 Subject: [PATCH] afs.c: Improve documentation of afs_socket_cookie. The old text had a few language issues and did not mention the fact that the socket cookie is written to the afs socket. --- afs.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/afs.c b/afs.c index 46af53f8..d5afc6d9 100644 --- a/afs.c +++ b/afs.c @@ -97,10 +97,11 @@ static char *current_mop; /* mode or playlist specifier. NULL means dummy mood * /** * A random number used to "authenticate" the connection. * - * para_server picks this number by random before forking the afs process. The - * command handlers write this number together with the id of the shared memory - * area containing the query. This way, a malicious local user has to know this - * number to be able to cause the afs process to crash by sending fake queries. + * para_server picks this number by random before it forks the afs process. The + * command handlers know this number as well and write it to the afs socket, + * together with the id of the shared memory area which contains the payload of + * the afs command. A local process has to know this number to abuse the afs + * service provided by the local socket. */ extern uint32_t afs_socket_cookie; -- 2.39.2