FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2025-06-16T02:49:36Z 2025-06-16T02:49:36Z Cy Schubert cy@FreeBSD.org 2025-06-10T20:07:32Z urn:sha1:78d4557a9b6d13ce6040255ec5f8875db351e9a0 MIT KRB5 does not support telnet. This is because telnet uses 3DES encryption, which requires 3DES encrypted keys in the KDC database. As MIT had deprecated and removed 3DES support about a decade ago, telnet is not supported. Sponsored by: The FreeBSD Foundation Reviewed by: markj Differential revision: https://reviews.freebsd.org/D50785 2024-07-15T22:43:39Z Warner Losh imp@FreeBSD.org 2024-07-15T04:46:32Z urn:sha1:e9ac41698b2f322d55ccf9da50a3596edb2c1800 This is a residual of the $FreeBSD$ removal. MFC After: 3 days (though I'll just run the command on the branches) Sponsored by: Netflix 2023-08-16T17:55:03Z Warner Losh imp@FreeBSD.org 2023-08-16T17:55:03Z urn:sha1:d0b2dbfa0ecf2bbc9709efc5e20baf8e4b44bbbf Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ 2021-10-04T09:38:24Z Baptiste Daroussin bapt@FreeBSD.org 2021-09-23T01:52:46Z urn:sha1:cbc83e378a7ee8f8aea9811906a2786a8f3bdeb3 Differential Revision: https://reviews.freebsd.org/D32098 2021-09-07T08:18:11Z Emmanuel Vadot manu@FreeBSD.org 2021-09-01T17:02:00Z urn:sha1:c7fd29f0f29ae3eb9d86cc019f6c1bab35634548 both telnet and telnetd aren't that useful nowadays but some might want them. Create a FreeBSD-telnet package so users have a choice to have them or not. Differential Revision: https://reviews.freebsd.org/D31791 Reviewed by: emaste 2019-07-15T14:19:39Z Warner Losh imp@FreeBSD.org 2019-07-15T14:19:39Z urn:sha1:01b01229540bfa1a250973da7c8a1a3d84853ca5 We remove IPSEC only in parts of the tree, and not others. RELEASE_CRUNCH to disable it has not kept up with all its uses. Remove it. Should there be a real need to disable IPSEC, one that hasn't shown up in the base system to date, it can be re-added behind a WITHOUT_IPSEC build option. 2017-03-12T18:58:44Z Warner Losh imp@FreeBSD.org 2017-03-12T18:58:44Z urn:sha1:a35f04fba2ebb8f86d4cbdc710c89a094572b08e Prefer ${SRCTOP}/foo over ${.CURDIR}/../../foo and ${SRCTOP}/usr.bin/foo over ${.CURDIR}/../foo for paths in Makefiles. Differential Revision: https://reviews.freebsd.org/D9932 Sponsored by: Netflix Silence on: arch@ (twice) 2014-11-25T14:29:10Z Baptiste Daroussin bapt@FreeBSD.org 2014-11-25T14:29:10Z urn:sha1:3e11bd9e2a2b1cbd4283c87c93e3cc75e3f2dacb Reduce overlinking 2014-08-19T15:04:32Z Bryan Drewery bdrewery@FreeBSD.org 2014-08-19T15:04:32Z urn:sha1:5608fd23c27fa1e8ee595d7b678cbfd35d657fbe 1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries. 2. Another 40% is fixed by generating _pic.a variants of various libraries. 3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases. 4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed. We likely do want to enable PIE by default (opt-out) for non-tree consumers (such as ports). For in-tree though we probably want to only enable PIE (opt-in) for common attack targets such as remote service daemons and setuid utilities. This is also a great performance compromise since ASLR is expected to reduce performance. As such it does not make sense to enable it in all utilities such as ls(1) that have little benefit to having it enabled. Reported by: kib 2014-07-17T18:24:34Z Brooks Davis brooks@FreeBSD.org 2014-07-17T18:24:34Z urn:sha1:80189b3b093749e26cb298735618c6633a2d26fc variants. This allows usable file system images (i.e. those with both a shell and an editor) to be created with only one copy of the curses library. Exp-run: antoine PR: 189842 Discussed with: bapt Sponsored by: DARPA, AFRL