| Age | Commit message (Collapse) | Author |
|---|
|
by R, so reintroduce it in the proper place.
spotted and diff by Sunil Nimmagadda
|
|
fix by Nathanael Rensen
|
|
features.
Feedback and OK jmc@
"Reads ok" krw@
|
|
stop referencing them in comments
|
|
ok krw@
|
|
dirent. (The memset in previous commit was both wrong and insufficient.)
problem with memset noted by brad@ and jsg@
ok millert@
|
|
Correct old style entries so nothing has to be done for the admin.
diff from Manuel Giraud (manuel (at) ledu-giraud.fr) Thanks!
|
|
|
|
|
|
Pointed out by bluhm@; no object change.
OK bluhm@, krw@
|
|
No object change.
|
|
Input bluhm@, OK krw@
|
|
ok krw@
|
|
ok miod@
|
|
in get_token(). Simplifies code and shrinks future diff.
No intentional functional change.
|
|
- fix a TAILQ corruption because of a use after free
- do not reinit the SSL engine since that fails
OK sthen, benno
|
|
encountering a carriage return in the input.
Found by jsg@ a long time ago in a respository far, far away.
|
|
this is largely based on src/sys/arch/alpha/alpha/mutex.c r1.14 and
src/sys/arch/sgi/sgi/mutex.c r1.15
always and explicitely record which cpu owns the lock (or NULL if
noone owns it). improve the mutex diagnostics/asserts so they operate
on the mtx_owner field rather than mtx_lock. previously the asserts
would assume the lock cpu owns the lock if any of them own the lock,
which blows up badly.
hppa hasnt got good atomic cpu opcodes, so this still relies on
ldcws to serialise access to the lock.
while im here i also shuffled the code. on MULTIPROCESSOR systems
instead of duplicating code between mtx_enter and mtx_enter_try,
mtx_enter simply loops on mtx_enter_try until it succeeds.
this also provides an alternative implementation of mutexes on
!MULTIPROCESSOR systems that avoids interlocking opcodes. mutexes
wont contend on UP boxes, theyre basically wrappers around spls.
we can just do the splraise, stash the owner as a guard value for
DIAGNOSTIC and return. similarly, mtx_enter_try on UP will never
fail, so we can just call mtx_enter and return 1.
tested by and ok kettenis@ jsing@
|
|
|
|
|
|
tweakable: there's no real point and these files support the 'include' option so
one can always get its config from whatever path... especially useful when
testing a new ruleset.
man page inputs from schwarze@
ok halex@ schwarze@ rpe@ deraadt@
|
|
thanks paul de weerd for pointers
|
|
or take a cast. Tweak error messages to also be consistant with
ping(8).
Change lower bound of '-h' to 0 from -1 at the request of florian@.
Tweaks and suggestions from, ok florian@
|
|
ok, though not neccessarily endorsed, from/by otto
tim van der molen further requested it be "king's day" and the removal
of antilles
while here i've used an article (*the* netherlands), here and in another
example
|
|
set ROFF_NEXT_CHILD, which is desirable for the final call to
mdoc_valid_post() - in case the target itself gets deleted, the
parse point may need this adjustment - but not for the intermediate
calls - if intermediate nodes get deleted, that mustn't clobber the
parse point. So move setting ROFF_NEXT_SIBLING to the proper place
in rew_last().
This fixes the assertion failure in jsg@'s afl test case 108/Apr27.
|
|
|
|
weird place. Move it to the obviously correct place.
Surprisingly, this didn't cause any misformatting in the test suite
or in any base system manuals, but i cannot believe the code was
really correct for all conceivable input, and it would be very hard
to verify. At the very least, it cannot have worked for man(7).
|
|
not just the body. In some unusual edge cases, this caused
the .Pp to become a sibling of the .Nm body inside the .Nm block.
|
|
|
|
|
|
From Hrvoje Popovski.
|
|
|
|
|
|
too; bz#1459 ok dtucker@
|
|
report error conditions. Teach sshpkt_fatal() about ECONNRESET.
Improves error messages on TCP connection resets. bz#2257
ok dtucker@
|
|
to be misapplied in match context;
bz#2272 diagnosis and original patch from Sami Hartikainen
ok dtucker@
|
|
with other =none options; bz#2288 from Jakub Jelen; ok dtucker@
|
|
list of active forwards; bz#2363, patch mostly by Yoann Ricordel;
ok dtucker@
|
|
ok dtucker@
|
|
a corresponding private key authentication being applied to other
authentication methods. Reported by halex@, ok markus@
|
|
on PermitUserEnv - always parse it, but only use the result if the
option is enabled. This prevents the syntax of authorized_keys changing
depending on which sshd_config options were enabled.
bz#2329; based on patch from coladict AT gmail.com, ok dtucker@
|
|
flags to check FREAD/FWRITE if needed. This will be used by fifo_poll
to avoid checking the write end of the fifo when the fd is read-only.
OK guenther@
|
|
Tested by jmatthew@
|
|
|
|
ok miod@
|
|
because the option names are case sensitive, but it just looks awful. so
expect just a little more from the reader...
|
|
change in ip_spd.c 1.59 makes it appear that there is a cut & pasto.
OK mikeb@
|
|
|
|
|
|
ok henning@ gilles@ deraadt@
|
