src/libexec/telnetd/Makefile, branch main

Remove telnetd

2022-09-28T18:53:49Z

The telnetd codebase is unmaintained and has a number of quality issues. Telnet has been largely supplanted by ssh. If needed, a port is available (net/freebsd-telnetd), but a more maintained implementation should be prefered. While the telnet client suffers from the same issues, it is deemed to be of lower risk and is required to connect to legacy devices, so it remains. Reviewed by: emaste, imp Differential Revision: https://reviews.freebsd.org/D36620

ncurses: chase dependency changes in the source tree

2021-10-04T09:38:24Z

Differential Revision: https://reviews.freebsd.org/D32098

pkgbase: Create a FreeBSD-telnet package

2021-09-07T08:18:11Z

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

These values already set by src.libnames.mk.

2017-10-31T00:03:25Z

MFC after: 2 weeks Sponsored by: Dell EMC Isilon

libexec: normalize paths using SRCTOP-relative paths or :H when possible

2017-03-04T11:28:03Z

This simplifies make logic/output MFC after: 1 month Sponsored by: Dell EMC Isilon

Convert to LIBADD

2014-11-25T21:18:18Z

Reduce overlinking

Add baud rate support to telnet(1)

2014-11-11T04:06:05Z

This implements part of RFC-2217 It's based off a patch originally written by Sujal Patel at Isilon, and contributions from other Isilon employees. PR: 173728 Phabric: D995 Reviewed by: markj, markm MFC after: 2 weeks Sponsored by: EMC / Isilon Storage Division

Revert r267233 for now. PIE support needs to be reworked.

2014-08-19T15:04:32Z

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

Replace all uses of libncurses and libtermcap with their wide character

2014-07-17T18:24:34Z

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

In preparation for ASLR [1] support add WITH_PIE to support building with -fPIE.

2014-06-08T17:29:31Z

This is currently an opt-in build flag. Once ASLR support is ready and stable it should changed to opt-out and be enabled by default along with ASLR. Each application Makefile uses opt-out to ensure that ASLR will be enabled by default in new directories when the system is compiled with PIE/ASLR. [2] Mark known build failures as NO_PIE for now. The only known runtime failure was rtld. [1] http://www.bsdcan.org/2014/schedule/events/452.en.html Submitted by: Shawn Webb Discussed between: des@ and Shawn Webb [2]