|
Revision tags: release/12.4.0, release/13.1.0, release/12.3.0 |
|
| #
0f0d52fd |
| 28-Nov-2021 |
Ed Maste <[email protected]> |
sbin: build ping if at least one of INET & INET6 is enabled
It does not build (and serves no purpose) if neither is true (i.e., building WITHOUT_INET and WITHOUT_INET6). Also add an explicit error
sbin: build ping if at least one of INET & INET6 is enabled
It does not build (and serves no purpose) if neither is true (i.e., building WITHOUT_INET and WITHOUT_INET6). Also add an explicit error in ping to make this case clear.
PR: 260082 Sponsored by: The FreeBSD Foundation
(cherry picked from commit a4ef9e58bc0c07110a54ba0fa88eb118c5377e6f)
OptionalObsoleteFiles: remove ping with INET & INET6 disabled
Reported by: kevans Fixes: a4ef9e58bc0c ("sbin: build ping if at least one of...") Sponsored by: The FreeBSD Foundation
(cherry picked from commit 0179739a0096c62cb3c9665d68246046255ab849)
show more ...
|
|
Revision tags: release/13.0.0 |
|
| #
3cde9171 |
| 26-Nov-2020 |
Alan Somers <[email protected]> |
Merge ping6 to ping
There is now a single ping binary, which chooses to use ICMP or ICMPv4 based on the -4 and -6 options, and the format of the address.
Submitted by: Ján Sučan <[email protected]
Merge ping6 to ping
There is now a single ping binary, which chooses to use ICMP or ICMPv4 based on the -4 and -6 options, and the format of the address.
Submitted by: Ján Sučan <[email protected]> Sponsored by: Google LLC (Google Summer of Code 2019) MFC after: Never Differential Revision: https://reviews.freebsd.org/D21377
show more ...
|
|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0 |
|
| #
f5a95d9a |
| 25-Jun-2019 |
Warner Losh <[email protected]> |
Remove NAND and NANDFS support
NANDFS has been broken for years. Remove it. The NAND drivers that remain are for ancient parts that are no longer relevant. They are polled, have terrible performance
Remove NAND and NANDFS support
NANDFS has been broken for years. Remove it. The NAND drivers that remain are for ancient parts that are no longer relevant. They are polled, have terrible performance and just for ancient arm hardware. NAND parts have evolved significantly from this early work and little to none of it would be relevant should someone need to update to support raw nand. This code has been off by default for years and has violated the vnode protocol leading to panics since it was committed.
Numerous posts to arch@ and other locations have found no actual users for this software.
Relnotes: Yes No Objection From: arch@ Differential Revision: https://reviews.freebsd.org/D20745
show more ...
|
| #
eb12b8ea |
| 26-Feb-2019 |
Simon J. Gerraty <[email protected]> |
Add verifying manifest loader for mac_veriexec
This tool will verify a signed manifest and load contents into mac_veriexec for storage
Sponsored by: Juniper Networks Differential Revision: D16575
|
| #
b252313f |
| 31-Jan-2019 |
Gleb Smirnoff <[email protected]> |
New pfil(9) KPI together with newborn pfil API and control utility.
The KPI have been reviewed and cleansed of features that were planned back 20 years ago and never implemented. The pfil(9) intern
New pfil(9) KPI together with newborn pfil API and control utility.
The KPI have been reviewed and cleansed of features that were planned back 20 years ago and never implemented. The pfil(9) internals have been made opaque to protocols with only returned types and function declarations exposed. The KPI is made more strict, but at the same time more extensible, as kernel uses same command structures that userland ioctl uses.
In nutshell [KA]PI is about declaring filtering points, declaring filters and linking and unlinking them together.
New [KA]PI makes it possible to reconfigure pfil(9) configuration: change order of hooks, rehook filter from one filtering point to a different one, disconnect a hook on output leaving it on input only, prepend/append a filter to existing list of filters.
Now it possible for a single packet filter to provide multiple rulesets that may be linked to different points. Think of per-interface ACLs in Cisco or Juniper. None of existing packet filters yet support that, however limited usage is already possible, e.g. default ruleset can be moved to single interface, as soon as interface would pride their filtering points.
Another future feature is possiblity to create pfil heads, that provide not an mbuf pointer but just a memory pointer with length. That would allow filtering at very early stages of a packet lifecycle, e.g. when packet has just been received by a NIC and no mbuf was yet allocated.
Differential Revision: https://reviews.freebsd.org/D18951
show more ...
|
|
Revision tags: release/12.0.0 |
|
| #
5952343e |
| 24-Jul-2018 |
Kyle Evans <[email protected]> |
Rename be(1) to bectl(8); continues to live in /sbin
Discussed with: rpokala, allanjude
|
| #
28f16a0f |
| 24-Jul-2018 |
Kyle Evans <[email protected]> |
Import libbe(3)/be(1) from socsvn/soc2017/kneitinger/libbe-head
|
| #
aa571745 |
| 24-Jun-2018 |
Eitan Adler <[email protected]> |
Makefiles: remove outdated comments
|
|
Revision tags: release/11.2.0 |
|
| #
f0f8a1af |
| 14-Jun-2018 |
Warner Losh <[email protected]> |
NVME support is only for x86 and powerpc64.
Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camco
NVME support is only for x86 and powerpc64.
Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camcontrol to define WITH_NVME for those platforms where we support nvme.
This should fix the newly introduced nvme files to camcontrol which were building everywhere.
Pointy Hat To: imp Sponsored by: Netflix
show more ...
|
| #
590682b6 |
| 12-Feb-2018 |
Warner Losh <[email protected]> |
Move devmatch to sbin from usr/sbin.
Since we want to use devmatch in context before a split /,/usr system has mounted /usr, move devmatch to /sbin.
Sponsored by: Netflix
|
| #
93b09f58 |
| 05-Nov-2017 |
Konstantin Belousov <[email protected]> |
Remove badsect(8).
Failure modes of the modern (that is, produced in the last 25 years) hard drives and SSDs made the utility outdated. Since the kernel interface to support it was removed in r3248
Remove badsect(8).
Failure modes of the modern (that is, produced in the last 25 years) hard drives and SSDs made the utility outdated. Since the kernel interface to support it was removed in r324853, cut the userspace remnants as well.
Discussed with: bde (who does not like the removal) Sponsored by: The FreeBSD Foundation MFC after: 2 weeks
show more ...
|
|
Revision tags: release/10.4.0, release/11.1.0 |
|
| #
01df7d10 |
| 06-Jul-2017 |
Enji Cooper <[email protected]> |
Remove SUBDIR ordering/uniquifying in *bin/Makefile
After the addition of SUBDIR.yes, uniquifying/ordering the SUBDIRs doesn't make a whole lot of sense, and it's in effect a half measure.
Ordering
Remove SUBDIR ordering/uniquifying in *bin/Makefile
After the addition of SUBDIR.yes, uniquifying/ordering the SUBDIRs doesn't make a whole lot of sense, and it's in effect a half measure.
Ordering SUBDIR (after adding SUBDIR.yes to it) in bsd.subdir.mk is a separate change that warrants more discussion/testing, because while the SUBDIR_PARALLEL work largely fixed dependency ordering for SUBDIRs, there might be downstream FreeBSD consumers that rely on the SUBDIR ordering.
MFC after: 2 months Reviewed by: bdrewery Differential Revision: D11398
show more ...
|
| #
a7dc3128 |
| 24-Apr-2017 |
Brooks Davis <[email protected]> |
Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the cas
Remove the NATM framework including the en(4), fatm(4), hatm(4), and patm(4) devices.
Maintaining an address family and framework has real costs when we make infrastructure improvements. In the case of NATM we support no devices manufactured in the last 20 years and some will not even work in modern motherboards (some newer devices that patm(4) could be updated to support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't require NATM support code. It is unclear if all these should remain, though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at least September 30, 2021. Improvements to the code in FreeBSD 11 are certainly welcome.
Reviewed by: philip Approved by: harti
show more ...
|
| #
480f31c2 |
| 10-Dec-2016 |
Konrad Witaszczyk <[email protected]> |
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDU
Add support for encrypted kernel crash dumps.
Changes include modifications in kernel crash dump routines, dumpon(8) and savecore(8). A new tool called decryptcore(8) was added.
A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dump configuration in the diocskerneldump_arg structure to the kernel. The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 for backward ABI compatibility.
dumpon(8) generates an one-time random symmetric key and encrypts it using an RSA public key in capability mode. Currently only AES-256-CBC is supported but EKCD was designed to implement support for other algorithms in the future. The public key is chosen using the -k flag. The dumpon rc(8) script can do this automatically during startup using the dumppubkey rc.conf(5) variable. Once the keys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/O control.
When the kernel receives the DIOCSKERNELDUMP I/O control it generates a random IV and sets up the key schedule for the specified algorithm. Each time the kernel tries to write a crash dump to the dump device, the IV is replaced by a SHA-256 hash of the previous value. This is intended to make a possible differential cryptanalysis harder since it is possible to write multiple crash dumps without reboot by repeating the following commands: # sysctl debug.kdb.enter=1 db> call doadump(0) db> continue # savecore
A kernel dump key consists of an algorithm identifier, an IV and an encrypted symmetric key. The kernel dump key size is included in a kernel dump header. The size is an unsigned 32-bit integer and it is aligned to a block size. The header structure has 512 bytes to match the block size so it was required to make a panic string 4 bytes shorter to add a new field to the header structure. If the kernel dump key size in the header is nonzero it is assumed that the kernel dump key is placed after the first header on the dump device and the core dump is encrypted.
Separate functions were implemented to write the kernel dump header and the kernel dump key as they need to be unencrypted. The dump_write function encrypts data if the kernel was compiled with the EKCD option. Encrypted kernel textdumps are not supported due to the way they are constructed which makes it impossible to use the CBC mode for encryption. It should be also noted that textdumps don't contain sensitive data by design as a user decides what information should be dumped.
savecore(8) writes the kernel dump key to a key.# file if its size in the header is nonzero. # is the number of the current core dump.
decryptcore(8) decrypts the core dump using a private RSA key and the kernel dump key. This is performed by a child process in capability mode. If the decryption was not successful the parent process removes a partially decrypted core dump.
Description on how to encrypt crash dumps was added to the decryptcore(8), dumpon(8), rc.conf(5) and savecore(8) manual pages.
EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU. The feature still has to be tested on arm and arm64 as it wasn't possible to run FreeBSD due to the problems with QEMU emulation and lack of hardware.
Designed by: def, pjd Reviewed by: cem, oshogbo, pjd Partial review: delphij, emaste, jhb, kib Approved by: pjd (mentor) Differential Revision: https://reviews.freebsd.org/D4712
show more ...
|
| #
97371ba2 |
| 29-Oct-2016 |
Andriy Gapon <[email protected]> |
zfsbootcfg: a simple tool to set next boot (one time) options for zfsboot
(gpt)zfsboot will read one-time boot directives from a special ZFS pool area. The area was previously described as "Boot Bl
zfsbootcfg: a simple tool to set next boot (one time) options for zfsboot
(gpt)zfsboot will read one-time boot directives from a special ZFS pool area. The area was previously described as "Boot Block Header", but currently it is know as Pad2, marked as reserved and is zeroed out on pool creation. The new code interprets data in this area, if any, using the same format as boot.config. The area is immediately wiped out. Failure to parse the directives results in a reboot right after the cleanup. Otherwise the boot sequence proceeds as usual.
zfsbootcfg writes zfsboot arguments specified on its command line to the Pad2 area of a disk identified by vfs.zfs.boot.primary_pool and vfs.zfs.boot.primary_vdev kenv variables that are set by loader during boot. Please see the manual page for more.
Thanks to all who reviewed, contributed and made suggestions! There are many potential improvements to the feature, please see the review for details.
Reviewed by: wblock (docs) Discussed with: jhb, tsoome MFC after: 3 weeks Relnotes: yes Differential Revision: https://reviews.freebsd.org/D7612
show more ...
|
|
Revision tags: release/11.0.1, release/11.0.0 |
|
| #
014db25b |
| 12-Aug-2016 |
Enji Cooper <[email protected]> |
Update ^/vendor/NetBSD/tests/dist to a more recent snapshot
Pulled on "Thu Aug 11 18:01:19 PDT 2016"
|
|
Revision tags: release/10.3.0 |
|
| #
c501d73c |
| 25-Feb-2016 |
Mariusz Zaborski <[email protected]> |
Convert casperd(8) daemon to the libcasper. After calling the cap_init(3) function Casper will fork from it's original process, using pdfork(2). Forking from a process has a lot of advantages: 1. We
Convert casperd(8) daemon to the libcasper. After calling the cap_init(3) function Casper will fork from it's original process, using pdfork(2). Forking from a process has a lot of advantages: 1. We have the same cwd as the original process. 2. The same uid, gid and groups. 3. The same MAC labels. 4. The same descriptor table. 5. The same routing table. 6. The same umask. 7. The same cpuset(1). From now services are also in form of libraries. We also removed libcapsicum at all and converts existing program using Casper to new architecture.
Discussed with: pjd, jonathan, ed, [email protected], emaste Partially reviewed by: [email protected], bdrewery Approved by: pjd (mentor) Differential Revision: https://reviews.freebsd.org/D4277
show more ...
|
| #
6f42d16f |
| 18-Nov-2015 |
Bryan Drewery <[email protected]> |
Convert to SUBDIR.yes format.
Reviewed by: imp Sponsored by: EMC / Isilon Storage Division Differential Revision: https://reviews.freebsd.org/D4182
|
|
Revision tags: release/10.2.0 |
|
| #
87d352d5 |
| 02-Feb-2015 |
Enji Cooper <[email protected]> |
Remove duplicate MK_ISCSI block and sort the conditional blocks so this error won't crop up again in the future
Reported by: gjb MFC after: 1 week
|
| #
c01f300b |
| 26-Jan-2015 |
Enji Cooper <[email protected]> |
Build sbin/iscontrol again if MK_ISCSI != no
MFC after: 13 days X-MFC with: r277675 Pointyhat to: me
|
| #
4e395054 |
| 26-Jan-2015 |
Enji Cooper <[email protected]> |
Add MK_HAST knob for building and installing hastd(8), et al
MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
|
| #
18cc3172 |
| 25-Jan-2015 |
Enji Cooper <[email protected]> |
Add MK_CCD knob for building and installing ccd(4), ccdconfig, etc
MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
|
| #
b29d6977 |
| 25-Jan-2015 |
Enji Cooper <[email protected]> |
Add MK_ISCSI knob for building the iscsi initiator, iscsi daemon, kernel modules, etc
MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division
|
| #
21060720 |
| 02-Dec-2014 |
Enji Cooper <[email protected]> |
Make ccd(4), et al conditional based on MK_CCD
|
| #
317fdbc6 |
| 30-Nov-2014 |
Enji Cooper <[email protected]> |
Build spppcontrol if MK_PPP != no
|