From d2cdd5f3d0dc05deb7381faaf3afcb0a877be8d6 Mon Sep 17 00:00:00 2001 From: Renzo Davoli Date: Tue, 24 Oct 2017 10:39:21 +0200 Subject: [PATCH] man page syntax bugfix: cado.1 scado.1 --- cado.1 | 2 +- scado.1 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/cado.1 b/cado.1 index a14d8c8..59a33c3 100644 --- a/cado.1 +++ b/cado.1 @@ -47,7 +47,7 @@ When \fBcado\fR runs is scado mode (by the option \fB-S\fR or \fB--scado\fR), if .br \fBcado\fR runs the command granting the required ambient capabilities without any further authentication request (it does not prompt for a password). -.SP +.SP 2 .SH OPTIONS .I cado diff --git a/scado.1 b/scado.1 index f268792..2b21d75 100644 --- a/scado.1 +++ b/scado.1 @@ -51,7 +51,7 @@ masks. For brevity, the \fBcap_\fR prefix of capabilities names can be omitted The \fIsha256_digest_of_the_executable\fR prevents \fITOCTTOU\fR attacks. When a user wants to run the file at \fIpath_of_the_executable_file\fR granting it some of the capabilities in the \fIcapability_list\fR, the permission is denied if -its sha256 digest does not match \fIsha256_digest_of_the_executable\R. +its sha256 digest does not match \fIsha256_digest_of_the_executable\fR. If there are only two colon (\fB:\fR) separated fields in a line, it means that the user trusts a priori the integrity of the file whose pathname is \fIpath_of_the_executable_file\fR.