| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
| |
fetching over http(s) and use the timestamps from the remote server's
Last-Modified header if available when saving local files
this makes it possible to mirror files better with ftp(1)
the new timestamp behaviour can be disabled with the new '-u' flag
ok sthen@, input from sthen@ and gnezdo@
|
|
|
|
| |
Fixes crash that can occur when an usb device is unplugged, found by edd@
|
| |
|
| |
|
|
|
|
|
|
|
| |
Remove a trailing white space, don't misspell misconfiguration and
use https.
ok jmc, claudio
|
|
|
|
|
| |
ok bket@ sthen@ (who initially suggested the if-not-native value under
a similar name)
|
|
|
|
| |
this does fix the grep case
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Fixes a bug where policies that only differ in their flow
configuration lead to a handshake error.
Found by claudio@
ok patrick@
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use ppoll(2) instead of poll(2) in default_route_index(). Using
ppoll(2) here forces us to use clock_gettime(2) to measure the
timeout, which is less error-prone than using time(3).
Part of a larger campaign in dhclient(8) to make "time stuff" more
accurate and robust.
Prompted by krw@. Based on a diff from krw@.
ok krw@
|
|
|
|
|
|
| |
variables used here instead of using the ones from config.c.
ok deraadt@, kn@
|
|
|
|
| |
OK bluhm@, claudio@, mpi@, semarie@
|
|
|
|
| |
ok eric jsing
|
| |
|
|
|
|
|
| |
needed for >= linux 5.9 dtbs on bbb
ok kettenis@
|
|
|
|
|
|
|
| |
short TCP segments or fragments encapsulated in ESP instead of
fragmented ESP packets. Pass the don't fragment flag down along
the stack so that dynamic routes with MTU are created eventually.
with and OK markus@; OK tobhe@
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allows to check the existence of a variable in predicates, making it
possible to trace syscall latency, as follow:
syscall:select:entry
{
@start[pid] = nsecs;
}
syscall:select:return
/@start[pid]/
{
@usecs = hist((nsecs - @start[pid]) / 1000);
delete(@start[pid]);
}
|
|
|
|
|
|
|
|
|
| |
bInterfaceNumber and bAlternateSetting as following:
ifaceidx -> ifaceno
altidx -> altno
Suggested and ok mpi@
|
|
|
|
|
| |
there are no other detached sessions to switch to, from Sencer Selcuk in
GitHub issue 2553.
|
|
|
|
|
|
|
| |
Otherwise this `pxi' can be killed by concurrent thread after context
switch caused by following netlock.
ok yasuoka@
|
|
|
|
|
|
| |
OpenBSD 6.7 npppd(8) can't work over tun(4).
ok yasuoka@
|
|
|
|
| |
ok bluhm@ dlg@
|
|
|
|
|
|
| |
clean up FILES while here
ok claudio for the former
|
| |
|
| |
|
|
|
|
|
|
|
| |
We are never updating this sub-tree. Knock out the collision in the simplest
way. diff from mortimer.
This is the last change required for -fno-common on all architectures,
thanks to mortimer for starting the effort and encouraging others.
|
| |
|
|
|
|
|
|
| |
Reduces spurious packet transmissions in situations with short timings.
Suggestions millert@, further suggestions & ok cheloha@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this is a significant (and breaking) reworking of the policy based
routing that pf can do. the intention is to make it as easy as
nat/rdr to use, and more robust when it's operating.
the main reasons for this change are:
- route-to, reply-to, and dup-to do not work with pfsync
this is because the information about where to route-to is stored in
rules, and it is hard to have a ruleset synced between firewalls,
and impossible to have them synced 100% of the time.
- i can make my boxes panic in certain situations using route-to
yeah...
- the configuration and syntax for route-to rules are confusing.
the argument to route-to and co is an interace name with an optional
ip address. there are several problems with this. one is that people
tend to think about routing as sending packets to peers by their
address, not by the interface they're reachable on. another is that
we currently have no way to synchronise interface topology information
between firewalls, so using an interface to say where packets go
means we can't do failover of these states with pfsync. another
is that a change in routing topology means a host may become
reachable over a different interface. tying routing policy to
interfaces gets in the way of failover and load balancing.
this change does the following:
- stores the route info in the state instead of the pf rule
this allows route-to to keep working when the ruleset changes, and
allows route-to info to be sent over pfsync. there's enough spare bits
in pfsync messages that the protocol doesnt break.
the caveat is that route-to becomes tied to pass rules that create
state, like rdr-to and nat-to.
- the argument to route-to etc is a destination ip address
it's not limited to a next-hop address (thought a next-hop can be a
destination address). this allows for the failover and load balancing
referred to above.
- deprecates the address@interface host syntax in pfctl
because routing is done entirely by IPs, the interface is derived from
the route lookup, not pf. any attempt to use the @interface syntax
will fail now in all contexts.
there's enthusiasm from proctor@ jmatthew@ and others
ok sashan@ bluhm@
|
|
|
|
|
|
|
|
| |
once they are received. Fixes memleak caused by duplicate
SSH2_MSG_KEX_DH_GEX_REQUEST (spotted by portable OpenSSH kex_fuzz
via oss-fuzz #30078).
ok markus@
|
| |
|
|
|
|
|
|
|
| |
instead of throwing an error. Fixes a bug where flows without
'dynamic' were skipped when 'config/request address' is used.
ok patrick@
|
|
|
|
| |
ok patrick@
|
|
|
|
| |
localhost.
|
|
|
|
|
|
| |
return -1, in which case we never need to suppress output.
noticed by Mark Patruck
|
|
|
|
| |
ok millert@
|
|
|
|
|
| |
Partly from Johann Oskarsson for Illumos/FreeBSD.
ok millert@
|
|
|
|
| |
ok millert@
|
|
|
|
| |
little bit more to do though before it can be enabled.
|
| |
|
| |
|
|
|
|
|
| |
returned string. OpenBSD's getline handles this just fine, but some
implementations used by -portable do not. ok djm@
|
| |
|
|
|
|
| |
ok denis
|
| |
|