Age | Commit message (Collapse) | Author |
|
that do repeated lookups. OK tb@
|
|
and group file lookups. This required a bit of reordering of the
file mode handling bits to deal with the const char *. OK tb@
|
|
to user_from_uid(3) and uid_from_user(3). This requires sprinkling
const in a few places to match the return value of user_from_uid(3).
OK tb@
|
|
that stdout and stderr are not closed.
from Nan Xiao
|
|
Pointed out by Clemens Goessnitzer (clemens AT goessnitzer.info), thanks!
|
|
Use consistent format in debug log for keys readied, offered and
received during public key authentication.
This makes it a little easier to see what is going on, as each message
now contains (where available) the key filename, its type and fingerprint,
and whether the key is hosted in an agent or a token.
|
|
revision 1.285
date: 2018/09/14 04:17:12; author: djm; state: Exp; lines: +47 -26; commitid: lflGFcNb2X2HebaK;
Use consistent format in debug log for keys readied, offered and
received during public key authentication.
This makes it a little easier to see what is going on, as each message
now contains the key filename, its type and fingerprint, and whether
the key is hosted in an agent or a token.
|
|
|
|
received during public key authentication.
This makes it a little easier to see what is going on, as each message
now contains the key filename, its type and fingerprint, and whether
the key is hosted in an agent or a token.
|
|
returning const char *.
|
|
feedback and ok tb@ jsing@ markus@
|
|
|
|
that are allowed for CA signatures. Notably excludes ssh-dsa.
ok markus@
|
|
against a supplied whitelist; ok markus
|
|
signature wrt loading and certification operations; ok markus@
|
|
ok markus@
|
|
using SHA256/base64 key fingerprints; ok markus@
|
|
(previously we logged only key ID and CA key fingerprint).
ok markus@
|
|
margins off for printing cells (like most everything else already
does). Problem reported by Thomas Sattler.
|
|
fix from Avi Halachmi.
|
|
|
|
changes. This stems from rdist stashing a pointer to the static
area used by getpw{ent,nam,uid} and using it to avoid repeating
passwd lookups when pw->pw_name matches the user to be looked up.
This relied on undefined behavior, and with the recent passwd
changes, is no longer possible as the old pointer will be invalidated.
A better approach is to use the upcoming uid_from_user(3) functions.
Found by and fix OK tim@
|
|
Noted by jca, thanks.
OK jca claudio
|
|
consistent to remote_connect() and getaddrinfo(3).
from Nan Xiao
|
|
via bz#2687.
|
|
multiplexing state, not just new sessions.
mention that confirmation is checked via ssh-askpass
|
|
from Nan Xiao; OK tb@
|
|
Kelly in GitHub issue 1460.
|
|
|
|
|
|
|
|
diff from asou at soum.co.jp
ok claudio kn
|
|
|
|
|
|
C-y, only use the top buffer if no text has previously been killed. This
and previous change promped by discussion with kn@.
|
|
|
|
By default, replacing "foo" with "bar" turns "FOO" into "BAR".
With case-replace turned off, "FOO" will turn into "bar".
OK florian@ tb@
|
|
No need to check for SSLv2/3 sessions when printing the tally mark.
Also do SSLv23_client_method -> TLS_client_method.
ok jsing@
|
|
showing an unknown error (since it's not defined) during fatal(), if it ever
an error occurs inside that condition.
OK deraadt@ markus@ djm@
|
|
OK dtucker@
|
|
jsing@ notes that this is not a complete solution, as we don't
account for retries or partial writes, but that this is a step
in a right direction.
May want to revisit this later to provide a complete solution.
ok jsing@
|
|
The 1.2em was an approximate equivalent of the 2n traditionally used
for terminal display, but it is much too wide for HTML rendering.
Issue reported by mikeb@.
|
|
|
|
than -1 on error. ok jca@
|
|
For example, ksh93(1) needs this for .B\n.SM.
|
|
someone ages ago and then more recently in GitHub issue 1449.
|
|
definition) request, used for example by groff_hdtbl(7).
This simplistic implementation may interact incorrectly
with the .tr (input character translation) request.
But come on, you are not only using .char *and* .tr, but you do so
with respect to the same character in the same manual page?
|
|
the scope remains open. Needed for example for groff_man(7).
|
|
ok tb
|
|
Needed for example by groff_hdtbl(7).
There are two limitations:
It does not support nested .while requests yet,
and each .while loop must start and end in the same scope.
The roff_parseln() return codes are now more flexible
and allow OR'ing options.
|