Age | Commit message (Collapse) | Author |
|
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.
|
|
Micah Cowan.
|
|
size. Allows use of FIFOs and whatnot. From Tiago Cunha, idea from Fulvio
Ciriaco.
|
|
should not wrap at the end of the text on the line but should be allowed to
move freely.
|
|
|
|
ok jmc@
|
|
|
|
|
|
|
|
Molen.
|
|
strange things can happen. So, freeze reading from the pty while in copy mode.
|
|
resolve the contradiction in the manual whether it's allowed or not
in favour of "not allowed" for now, shelving my diff to support
nested displays in mandoc(1) for later consideration.
Found by and unbreaking the build with mandoc(1).
Feedback and OK jmc@
|
|
* corrected .Vt handling (spotted by Joerg Sonnenberger)
* corrected .Xr argument handling (based on my patch)
* removed \\ escape sequence (because it is for low-level roff only)
* warn about trailing whitespace (suggested by jmc@)
* -Txhtml support
* and some general cleanup and doc improvements
|
|
line, from Micah Cowan.
|
|
|
|
by and fix from Micah Cowan.
|
|
|
|
|
|
instance. Now, the -f option sets the MIDI device (instead of the
sequencer(4) device). The -d and -l options were removed.
|
|
from Micah Cowan.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
when chrooting; reported by danh AT wzrd.com; ok dtucker@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20/pkcs-11v2-20.pdf
ssh(1) and ssh-keygen(1) use dlopen(3) directly to talk to a PKCS#11
provider (shared library) while ssh-agent(1) delegates PKCS#11 to
a forked a ssh-pkcs11-helper process.
PKCS#11 is currently a compile time option.
feedback and ok djm@; inspired by patches from Alon Bar-Lev
|
|
tmux. From clemens fischer.
|