| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
MFH (r310823): fix multi-line CONNECT responses
PR: 112515 173451 194483 209546
(cherry picked from commit 01bace6361f834a727e24dcc7434e8f91ac69f5b)
|
|\ |
|
| |
| |
| |
| |
| | |
Noticed by: gordon
Approved by: so
|
| |
| |
| |
| |
| |
| | |
Boot compatibility improvements with Azure VMs. [EN-17:06]
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
jhb pointed out that (struct ifnet) is part of the network driver KBI, and
thus the offsets of internal fields must not change. Therefore, move the new
"if_hw_addr" field to the end, and consume one of the "if_pspare"s; that's
what they're there for. Because netmap on stable/10 uses "if_pspare[0]", the
new field replaces the *last* element of that array; that way,
offsetof(if_pspare) is unchanged compared to before r318430.
PR: 194386
Reviewed by: jhb
Pointyhat to: rpokala
Sponsored by: Panasas
(cherry picked from commit 2f103d239c07e4f88b9852f3b8689f100d7a31d0)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a way to retrive it
NOTE: Due to restructuring, the merges didn't apply cleanly; the resulting
change is almost identical to what went into stable/11, but in some cases in
different locations.
The MAC address reported by `ifconfig ${nic} ether' does not always match
the address in the hardware, as reported by the driver during attach. In
particular, NICs which are components of a lagg(4) interface all report the
same MAC.
When attaching, the NIC driver passes the MAC address it read from the
hardware as an argument to ether_ifattach(). Keep a second copy of it, and
create ioctl(SIOCGHWADDR) to return it. Teach `ifconfig' to report it along
with the active MAC address.
PR: 194386
(cherry picked from commit 2ce46e31d62424593e08c3853efe8c1e9283aba2)
|
|\ \
| |/ |
|
| |
| |
| |
| |
| | |
Security: FreeBSD-SA-17:04.ipfilter
Approved by: so
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| | |
Xen migration enhancements. [EN-17:05]
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When forwarding pf tracks the size of the largest fragment in a fragmented
packet, and refragments based on this size.
It failed to ensure that this size was a multiple of 8 (as is required for all
but the last fragment), so it could end up generating incorrect fragments.
For example, if we received an 8 byte and 12 byte fragment pf would emit a first
fragment with 12 bytes of payload and the final fragment would claim to be at
offset 8 (not 12).
We now assert that the fragment size is a multiple of 8 in ip6_fragment(), so
other users won't make the same mistake.
Reported by: Antonios Atlasis <aatlasis at secfu net>
MFC after: 3 days
(cherry picked from commit 4f3397263b95a45dd58e2be3a566029f8841cace)
|
| |
| |
| |
| | |
This reverts commit 85456f63ff840d61764348265c2fe0242a22b859.
|
| |
| |
| |
| |
| |
| | |
Ticket #7378
(cherry picked from commit f2504b01d55b5cd3c625058869c4b9df1cf4525e)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
pf: Fix a crash in low-memory situations
If the call to pf_state_key_clone() in pf_get_translation() fails (i.e. there's
no more memory for it) it frees skp. This is wrong, because skp is a
pf_state_key **, so we need to free *skp, as is done later in the function.
Getting it wrong means we try to free a stack variable of the calling
pf_test_rule() function, and we panic.
(cherry picked from commit 9c6c619e748c0e1da35441d443ddf41cd4c4f30d)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add new USB ID.
While at it remove some whitespaces.
Submitted by: Jose Luis Duran <jlduran@gmail.com>
PR: 213110
(cherry picked from commit add9d7e968f91eb512407c01eea9fb464a5c482d)
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Approved by: so
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
Security: FreeBSD-SA-17:01.openssh
Security: CVE-2016-10009
Security: CVE-2016-10010
Approved by: so
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Approved by: so
|
| |
| |
| |
| |
| |
| | |
PR: 215105
Submitted by: <jtd2004a sbcglobal.net>
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix link_ntoa(3) buffer overflow in libc. [SA-16:37]
Fix possible escape from bhyve(8) virtual machine. [SA-16:38]
Fix warnings about valid time zone abbreviations. [EN-16:19]
Update timezone database information. [EN-16:20]
Security: FreeBSD-SA-16:36.telnetd
Security: FreeBSD-SA-16:37.libc
Security: FreeBSD-SA-16:38.bhyve
Errata Notice: FreeBSD-EN-16:19.tzcode
Errata Notice: FreeBSD-EN-16:20.tzdata
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note: because of what appears to be a missing MFC to stable branches,
these patches were generated by doing:
% rsync -av stable/10/contrib/tzdata releng/10.x/contrib/tzdata
% svn add releng/10.x/contrib/tzdata
Errata Notice: EN-16:19
Submitted by: gjb
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Incorporate a change from OpenBSD by millert@OpenBSD.org
Don't warn about valid time zone abbreviations. POSIX
through 2000 says that an abbreviation cannot start with ':', and
cannot contain ',', '-', '+', NUL, or a digit. POSIX from 2001
on changes this rule to say that an abbreviation can contain only
'-', '+', and alphanumeric characters from the portable character
set in the current locale. To be portable to both sets of rules,
an abbreviation must therefore use only ASCII letters." Adapted
from tzcode2015f.
Errata Notice: EN-16:19.tzcode
Submitted by: bapt
Approved by: so
|
| |
| |
| |
| | |
[1] https://lists.freebsd.org/pipermail/freebsd-net/2015-June/042530.html
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fix OpenSSL remote DoS vulnerability. [SA-16:35]
Security: FreeBSD-SA-16:33.openssh
Security: FreeBSD-SA-16:35.openssl
Approved by: so
|
| |
| |
| |
| |
| |
| |
| | |
based on passing incorrect parameters to sysarch(2).
Security: SA-16:15
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Due to increased parallelism and optimizations in several parts of the
system, the previously latent bugs in VM become much easier to trigger,
affecting a significant number of the FreeBSD users. The exact technical
details of the issues are provided in the commit messages of the merged
revisions, which are listed below with short summaries.
r301184 prevent parallel object collapses, fixes object lifecycle
r301436 do not leak the vm object lock, fixes overcommit disable
r302243 avoid the active object marking for vm.vmtotal sysctl, fixes
"vodead" hangs
r302513 vm_fault() race with the vm_object_collapse(), fixes spurious
SIGSEGV
r303291 postpone BO_DEAD, fixes panic on fast vnode reclaim
Approved by: so
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
The three files affected were tests and aren't normally built so this
had no user-facing effect in the normal case.
Approved by: so
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fix multiple portsnap vulnerabilities. [SA-16:30]
Fix multiple libarchive vulnerabilities. [SA-16:31]
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fragmented UDP and ICMP packets were corrupted if a firewall with reassembling
feature (like pf'scrub) is enabled on the bridge. This patch fixes corrupted
packet problem and the panic (triggered easly with low RAM) as explain in PR
185633.
bridge_pfil and bridge_fragment relationship:
bridge_pfil() receive (IN direction) packets and sent it to the firewall The
firewall can be configured for reassembling fragmented packet (like pf'scrubing)
in one mbuf chain when bridge_pfil() need to send this reassembled packet to the
outgoing interface, it needs to re-fragment it by using bridge_fragment()
bridge_fragment() had to split this mbuf (using ip_fragment) first then
had to M_PREPEND each packet in the mbuf chain for adding Ethernet
header.
But M_PREPEND can sometime create a new mbuf on the begining of the mbuf chain,
then the "main" pointer of this mbuf chain should be updated and this case is
tottaly forgotten. The original bridge_fragment code (Revision 158140,
2006 April 29) came from OpenBSD, and the call to bridge_enqueue was
embedded. But on FreeBSD, bridge_enqueue() is done after bridge_fragment(),
then the original OpenBSD code can't work as-it of FreeBSD.
PR: 185633
Submitted by: Olivier Cochard-Labbé
Differential Revision: https://reviews.freebsd.org/D7780
(cherry picked from commit a8a1202774e288fb88de8422397f7ff398f7e3fb)
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix overflow check in BN_bn2dec()
Fix an off by one error in the overflow check added by 07bed46
("Check for errors in BN_bn2dec()").
This fixes a regression introduced in SA-16:26.openssl.
Submitted by: jkim
PR: 212921
Approved by: so
|
| |
| |
| |
| |
| |
| |
| |
| | |
Submitted by: svenauhagen at github
MFC after: 3 days
Sponsored by: Rubicon Communications, LLC (Netgate)
(cherry picked from commit aa0f947239bb1137e935d123012dedab216cca27)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
pf: Map hook returns onto the correct error values
pf returns PF_PASS, PF_DROP, ... in the netpfil hooks, but the hook callers
expect to get E<foo> error codes.
Map the returns values. A pass is 0 (everything is OK), anything else means
pf ate the packet, so return EACCES, which tells the stack not to emit an ICMP
error message.
PR: 207598
(cherry picked from commit 26d31e281678303d3071eb6fbac74b22036f44c5)
|
|\ \
| |/ |
|
| |
| |
| |
| |
| | |
Approved by: so
Security: FreeBSD-SA-16:26.openssl
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| | |
Submitted by: Dexuan Cui <decui microsoft.com>, gjb
Approved by: so
|
| |
| |
| |
| |
| |
| | |
Hyper-V. Ticket #6446"
This reverts commit 95be4fb0378e88b4a64a2da93e8ef4611475a916.
|
| |
| |
| |
| | |
2.3.2-devel to 2.3.2-rel
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
Fix freebsd-update(8) support of FreeBSD 11.0 release
distribution. [EN-16:09]
Approved by: so
|
| | |
|
| | |
|