On Fri, Aug 03, 2018 at 03:49:04PM -0500, Kris Katterjohn wrote:
> Hey,
>
> The cu(1) tilde escapes ~C, ~R, ~X, ~$ and ~> are not allowed in
> restricted mode; however, the man page states that ~D is not allowed
> and omits the fact that ~> is not allowed.
>
> I have a patch below to correct this.
>
> Cheers,
> Kris Katterjohn
>
morning.
would it make more sense to just list under -r which commands are not
allowed, rather than repeating the text everywhere?
currently -r says
This prevents all local filesystem operations and command
executions.
is that not enough? i.e. can;t we just zap all the "this command is not
allowed" text?
jmc
> Index: cu.1
> ===================================================================
> RCS file: /cvs/src/usr.bin/cu/cu.1,v
> retrieving revision 1.17
> diff -u -p -r1.17 cu.1
> --- cu.1 10 Dec 2017 07:34:38 -0000 1.17
> +++ cu.1 3 Aug 2018 20:38:29 -0000
> @@ -112,6 +112,7 @@ Only the connection is dropped \(en the
> Copy file from local to remote.
> .Nm
> prompts for the name of a local file to transmit.
> +This command is not allowed in restricted mode.
> .It Ic ~$
> Pipe the output from a local
> .Ux
> @@ -142,7 +143,6 @@ file descriptors:
> This command is not allowed in restricted mode.
> .It Ic ~D
> Deassert the data terminal ready (DTR) line briefly.
> -This command is not allowed in restricted mode.
> .It Ic ~R
> Record all output from the remote system to a file.
> If the given file already exists, it is appended to.
>
