search for: mandoc

Hi, On systems that have mandoc installed but are missing an nroff binary, the configure script will fall back to pre-formatted manual pages despite the fact that mandoc could be used. The proposed patch adds mandoc as a valid formatter to configure.ac. As mandoc supports the -mdoc flag, it can simply be added to the list of nro...

What is the canonical link to Reference of "ServerAliveInterval"? Background: I want to write an answer at serverfault (Q-A Site). I want to avoid copy+pasting. I would like to lead the new comer to the canonical reference. Regards, Thomas G?ttler -- Thomas Guettler http://www.thomas-guettler.de/

...n in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the *BSDs and some others. In particular, there is nothing to install or reconfigure on most systems - both formats can be rendered with man(1) or processed into plaintext, html, pdf, or ps (or even into markdown, with mandoc(1)). The main point is that mdoc(7) allows for constructs like ....

Hi, I am sorry about this stupid question but after compilation of openssh-2.3.0p1 the manpages were installed but a man ssh gives only unstructured response without underlined lines etc. A nroff -man sshd.8 gives the same output but the contents of the file shows a nroff-format. Any ideas? My system is a HP-UX 11.000 with the pam-patch. regards Stephan -- LDS Brandenburg Dr. Stephan Hendl

Arnout Engelen: > I noticed the square brackets in `destination [command [argument...]` > were not balanced, But they are. Not only with mandoc(1), but also with groff(1). destination [command [argument ...]] -- Christian "naddy" Weisgerber naddy at mips.inka.de

...=============================== RCS file: /cvsroot/src/crypto/dist/ssh/moduli.5,v retrieving revision 1.8 retrieving revision 1.9 diff -d -p -u -r1.8 -r1.9 --- moduli.5 4 Jul 2003 21:56:48 -0000 1.8 +++ moduli.5 7 Feb 2005 12:26:56 -0000 1.9 @@ -31,7 +31,7 @@ .\" .\" Manual page, using -mandoc macros .\" -.Dd July 28, 1997 +.Dd February 7, 2005 .Dt MODULI 5 .Os .Sh NAME @@ -140,11 +140,16 @@ Specifies the best generator for a Diffi .Fa Modulus : hex string . The prime modulus. .Pp -The file is searched for moduli that meet the appropriate +The file should be searched for modu...

On 13 August 2018 at 15:06, Val Baranov <val.baranov at duke.edu> wrote: [...] > test_utf8: ........................ > regress/unittests/utf8/tests.c:48 test #25 "c_esc" > ASSERT_INT_EQ(len, wantlen) failed: > len = -1 > wantlen = 5 This boils down to meaning OpenSSH's smnprintf call failed for the string "\033x" instead of returning the

...n in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the *BSDs and some others. In particular, there is nothing to install or reconfigure on most systems - both formats can be rendered with man(1) or processed into html or pdf or ps. The main point is that mdoc(7) allows for constructs like .Op Fl f Ar arg meaning there is an optional ...

Version info: OpenSSH_7.3p1, OpenSSL 1.0.2i 22 Sep 2016, Arch linux The ssh-agent.1 man page seems to have an indentation oddity, at least, as formatted with recent Arch linux manpage toolset. Here's what appears in the formatted output just after the description of the the "-t" option: ---------- Begin formatted output ------------------------------------- -t life

...osing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. See a version of nsd-checkzone.8 below as an example. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the *BSDs and some others. In particular, there is nothing to install or reconfigure on most systems - both formats can be both rendered with existing man(1) implemnetations and processed into plaintext, html, pdf, ps and possibly other formats. The main point is that mdoc(7) allows for cons...

...p-bpf sandbox, allow mprotect(2) with PROT_(READ|WRITE|NONE) only. This syscall is used by some hardened heap allocators. Github PR#142 * sshd(8): in the Linux seccomp-bpf sandbox, allow the s390-specific ioctl for ECC hardware support. * All: use "doc" man page format if the mandoc(1) tool is present on the system. Previously configure would not select the "doc" man page format if mandoc was present but nroff was not. * sshd(8): don't install duplicate STREAMS modules on Solaris; check if STREAMS modules are already installed on a pty before installin...

...that is all that is needed. Reminds me of Question #2: how is your definition of POSIX different from ISO8859-1 (and/or ISO8859-15, the "UK" or EN_US variant)? > If you worry that some target system might not have a en_US.UTF-8 > locale installed, you can look at > > http://mandoc.bsd.lv/cgi-bin/cvsweb/configure?rev=HEAD > > for a way to autodetect a suitable UTF-8 locale - look for UTF8_LOCALE > in that script. > > But that may be overkill for OpenSSH. Just recklessly forcing > LC_CTYPE=en_US.UTF-8 may be good enough for OpenSSH's purposes. > If th...

I noticed the square brackets in `destination [command [argument...]` were not balanced, this balances them. Signed-off-by: Arnout Engelen <arnout at bzzt.net> --- ssh.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ssh.1 b/ssh.1 index 710d3d4e6..f3e5f3115 100644 --- a/ssh.1 +++ b/ssh.1 @@ -65,7 +65,7 @@ .Op Fl W Ar host : Ns Ar port .Op Fl w Ar local_tun Ns Op : Ns

...Severity: enhancement Priority: P5 Component: Documentation Assignee: unassigned-bugs at mindrot.org Reporter: chris at chrullrich.net (This is based on the text currently available at https://man.openbsd.org/sshd_config, which looks rather similar to the mandoc source in CVSweb.) >From the sshd_config(5) man page's section on Match: > The available criteria are User, Group, Host, LocalAddress, > LocalPort, RDomain, and Address The manual does not explain what each of these criteria matches against. Most of them are fairly simple, I think,...

http://bugzilla.mindrot.org/show_bug.cgi?id=1202 Summary: Missing instructions for building from CVS Product: Portable OpenSSH Version: 4.3p2 Platform: Other URL: http://openssh.org/portable.html OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Documentation

Hello, the man pages for openssh-2.3.0p1 look bad on our Tru64 Unix V4.0E systems. (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine. It is intended to replace rlogin and rsh, and provide secure encrypted communica- tions between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP ports can also be

Hi Team, I'm looking to "upgrade" my sites ssh installation from the original. I have built openssh-2.3.0p1 and it looks good. I am puzzled as to why there are so many source distributions? However, that is not why am writing - the man pages provided do not format with either Solaris 'nroff -man' or 'groff -man'. What am I missing here? Thanks for your help. Scott

...t", as opposed to the physical > markup like "put this in italics and add brackets" in man(7). > See a proposed rewrite of ogginfo.1 below as an example. > > The language itself is well supported for a long time by groff -mdoc > (being the case on most Linuxes) and by mandoc (on BSDs). > > I am willing to do it, please let me know. > > Your happy user > > Jan > > > .Dd "June 20, 2014" > .Dt OGGINFO 1 > .Os > .Sh NAME > .Nm ogginfo > .Nd display information about Ogg files and check their validity > .Sh SYNO...

...p-bpf sandbox, allow mprotect(2) with PROT_(READ|WRITE|NONE) only. This syscall is used by some hardened heap allocators. Github PR#142 * sshd(8): in the Linux seccomp-bpf sandbox, allow the s390-specific ioctl for ecc hardware support. * All: use "doc" man page format if the mandoc(1) tool is present on the system. Previously configure would not select the "doc" man page format if mandoc was present but nroff was not. * sshd(8): don't install duplicate STREAMS modules on Solaris; check if STREAMS modules are already installed on a pty before installin...

....PP before .SH, but that does > no harm. mdoc2man.awk is a terrible hack and not a proper parser > in the first place, so we shouldn't expect beauty in its output. > If the output is correct and portable, that's good enough. At some > point, we should replace mdoc2man.awk with mandoc -Tman anyway. > The last time i tried, there was still some work to do, so that > won't be instantaneous. At least on Linux systems, wouldn't using man/groff's built-in mdoc support also be good enough? -- Mantas Mikul?nas <grawity at gmail.com>