credential-cache--daemon: disallow relative socket path
Relative socket paths are dangerous since the user cannot generally control when the daemon starts (initially, after a timeout, kill or crash). Since the daemon creates but does not delete the socket directory, this could lead to spurious directory creation relative to the users cwd. Suggested-by: Jeff King <peff@peff.net> Signed-off-by: Jon Griffiths <jon_p_griffiths@yahoo.com> Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
a6e5e2864f
commit
bd93b8d9be
@ -262,6 +262,9 @@ int main(int argc, const char **argv)
|
||||
if (!socket_path)
|
||||
usage_with_options(usage, options);
|
||||
|
||||
if (!is_absolute_path(socket_path))
|
||||
die("socket directory must be an absolute path");
|
||||
|
||||
init_socket_directory(socket_path);
|
||||
register_tempfile(&socket_file, socket_path);
|
||||
|
||||
|
Reference in New Issue
Block a user