Age | Commit message (Collapse) | Author |
|
if and only if something was printed on that line.
This avoids double line breaks after nested lists
while still breaking lines after items with empty body.
|
|
Making pages look better and helping comparisons with groff output.
Note that proper hyphenation is postponed for now because it doesn't
really help the switch.
|
|
they are present; feedback and ok jmc@
|
|
|
|
|
|
|
|
imorgan AT nas.nasa.gov
|
|
format section and rework it a bit; requested by jmc@
|
|
|
|
|
|
|
|
|
|
page mentions and '-6' related code. Pointed out by Sebastian Rother.
ok deraadt@ henning@
|
|
|
|
|
|
are trusted to authenticate users (in addition than doing it per-user
in authorized_keys).
Add a RevokedKeys option to sshd_config and a @revoked marker to
known_hosts to allow keys to me revoked and banned for user or host
authentication.
feedback and ok markus@
|
|
ok jmc@
|
|
value explicitly instead of the fatal()-causing buffer_get_string_ptr()
|
|
|
|
"from=cert-authority". spotted by imorgan AT nas.nasa.gov
|
|
|
|
principal names and constraints
|
|
|
|
appease it.
|
|
and do not emulate groff's habit of printing garbage either,
but just print the wanted information even though the format
must be sacrificed because it won't fit.
|
|
and effectively unlimit the width of literal displays.
Following this traditional behaviour allows for automatic output
comparisons.
|
|
and .Vb/.Ve (similar to .nf/.fi) in man(7) mode.
These are not intended to be used manually, but they allow us to
properly render man(7) code autogenerated by pod2man(1),
making Perl and OpenSSL happy in our tree.
|
|
When a text line or a non-block macro line in the source code ends
in any of ".!?", consider that an end of sentence (EOS).
This makes Jason's rule "new sentence, new line" even more important.
Let the parser detect the EOS and insert a token into the AST.
Let the -Tascii frontend render the EOS token as a double space before
the next word.
|
|
[1-9] in vi mode, or M-[1-9] in emacs mode.
From Micah Cowan, tweaked a little by me.
|
|
macros after closing delimiters only, not after opening ones. Besides,
neither roff nor old nor new groff consider braces { } as delimiters.
This fixes some frequent misrenderings by mandoc,
for example ".Ql (" being rendered as "`'(" instead of "`('".
|
|
the cursor to the end of a wrapped line (if present) and in rectangle
mode it toggles between the end of the text and the last cell on the
line.
From Micah Cowan.
|
|
values can be stored in the cached terminal attributes rather than the
requested (untranslated) values. Prevents tmux clearing and setting the
attributes for every character when using aixterm colours.
|
|
|
|
|
|
command with -v. Make a second -v cause printing of raw feature
data and a full list of profiles. A few minor tweaks to the feature
bitmap handling. Helps in debugging media problems in cdio.
Suggestions from fgsch@, man page fixes from jmc@ as usual.
ok beck@ deraadt@
|
|
patch from daniel malament in pr 6235
ok millert@
|
|
of the response (for count == 1 only the hex version was printed). Make
things consistent and match the docs by only printing the hex mode even
if count > 1. OK otto@
|
|
Pointed out by obsd at happyjack.org, fix based on a diff from kili@.
ok deraadt
|
|
|
|
OpenSSH certificate key types are not X.509 certificates, but a much
simpler format that encodes a public key, identity information and
some validity constraints and signs it with a CA key. CA keys are
regular SSH keys. This certificate style avoids the attack surface
of X.509 certificates and is very easy to deploy.
Certified host keys allow automatic acceptance of new host keys
when a CA certificate is marked as trusted in ~/.ssh/known_hosts.
see VERIFYING HOST KEYS in ssh(1) for details.
Certified user keys allow authentication of users when the signing
CA key is marked as trusted in authorized_keys. See "AUTHORIZED_KEYS
FILE FORMAT" in sshd(8) for details.
Certificates are minted using ssh-keygen(1), documentation is in
the "CERTIFICATES" section of that manpage.
Documentation on the format of certificates is in the file
PROTOCOL.certkeys
feedback and ok markus@
|
|
This commit corresponds to what jmc@ did in share/tmac/mdoc/doc-common
and share/man/man7/mdoc.samples.7 on January 24.
|
|
used as a label, not "the first line following", so allow (some kinds of)
intervening macros - some people actually put macros in between.
On the other hand, when there is no text line before the next block macro,
that is, when the .TP block ends without any text line, then something *is*
broken, so still error out in that case.
|
|
The trick is to not switch from the .It header to the body at EOL, but,
in case an explicit block macro follows, at the end of the block.
|
|
issue--od(1) and hexdump(1) behave as expected. From FreeBSD.
|
|
|
|
entirely.
|
|
|
|
in the end simply changing Oo Xo Oo Oc Oc Xc to Oo Xo Oo Oc Xc Oc.
I tried five different variants without the Xo/Xc, because there is
no real reason why Xo/Xc should be needed here, and two additional
variants with Xo/Xc that look more pretty than what i'm now committing.
All seven alternatives work both with mandoc and groff 1.20.1, but
all seven trigger various different bugs in our old groff, and we
still need to remain compatible with our old groff right now.
ok jmc@ sobrado@
|
|
|
|
command in sudoers instead of checking the user-supplied command
for a slash.
|