| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
MFC after: 2 weeks
Sponsored by: Dell EMC Isilon
Notes:
svn path=/head/; revision=325178
|
| |
|
|
|
|
|
|
|
|
| |
This simplifies make logic/output
MFC after: 1 month
Sponsored by: Dell EMC Isilon
Notes:
svn path=/head/; revision=314653
|
| |
|
|
|
|
|
| |
Reduce overlinking
Notes:
svn path=/head/; revision=275077
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=274364
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=270168
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=268804
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <lattera@gmail.com>
Discussed between: des@ and Shawn Webb [2]
Notes:
svn path=/head/; revision=267233
|
| |
|
|
|
|
|
|
|
|
|
|
| |
remove the now-redundant checks for RELEASE_CRUNCH. This originally
was defined for building smaller sysinstall images, but was later also
used by picobsd builds for a similar purpose. Now that we've moved
away from sysinstall, picobsd is the only remaining consumer of this
interface. Adding these two options reduces the RELEASE_CRUNCH
special cases in the tree by half.
Notes:
svn path=/head/; revision=267147
|
| |
|
|
|
|
|
| |
from the latter.
Notes:
svn path=/head/; revision=265420
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some time ago I got some reports MPSAFE TTY broke telnetd(8). Even
though it turned out to be a different problem within the TTY code, I
spotted a small issue with telnetd(8). Instead of allocating PTY's using
openpty(3) or posix_openpt(2), it used its own PTY allocation routine.
This means that telnetd(8) still uses /dev/ptyXX-style devices.
I've also increased the size of line[]. Even though 16 should be enough,
we already use 13 bytes ("/dev/pts/999", including '\0'). 32 bytes gives
us a little more freedom.
Also enable -DSTREAMSPTY. Otherwise telnetd(8) strips the PTY's pathname
to the latest slash instead of just removing "/dev/" (e.g. /dev/pts/0 ->
0, instead of pts/0).
Reviewed by: rink
Notes:
svn path=/head/; revision=184935
|
| |
|
|
|
|
|
| |
all non-style changes made by heimdal to our own libgssapi.
Notes:
svn path=/head/; revision=178828
|
| |
|
|
|
|
|
|
|
|
| |
crunched floppies, but they can be included as options in
src/release/picobsd (omitted by default though.) Therefore
preserve the RELEASE_CRUNCH knob in their Makefiles, but
tell its real purpose in a comment.
Notes:
svn path=/head/; revision=160866
|
| |
|
|
|
|
|
| |
All the dependencies are satisfied now in <bsd.own.mk>.
Notes:
svn path=/head/; revision=160854
|
| |
|
|
|
|
|
|
|
| |
so its Makefile needn't test for RELEASE_CRUNCH.
Suggested by: ru
Notes:
svn path=/head/; revision=160853
|
| |
|
|
|
|
|
| |
Apply style.Makefile(5).
Notes:
svn path=/head/; revision=160743
|
| |
|
|
|
|
|
|
|
|
|
| |
http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
The src.conf(5) manpage is to follow in a few days.
Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
Notes:
svn path=/head/; revision=156813
|
| |
|
|
|
|
|
| |
Discussed with: ru
Notes:
svn path=/head/; revision=147225
|
| |
|
|
| |
Notes:
svn path=/head/; revision=139113
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
of releases. The -DNOCRYPT build option still exists for anyone who
really wants to build non-cryptographic binaries, but the "crypto"
release distribution is now part of "base", and anyone installing from a
release will get cryptographic binaries.
Approved by: re (scottl), markm
Discussed on: freebsd-current, in late April 2004
Notes:
svn path=/head/; revision=133196
|
| |
|
|
|
|
|
|
| |
the crunched binary) get a non-cryptographic telnet. This is overkill
in that it covers stuff that is not normally used in a crunched binary.
Notes:
svn path=/head/; revision=117973
|
| |
|
|
|
|
|
| |
distribution is used. This only affects release-building.
Notes:
svn path=/head/; revision=117953
|
| |
|
|
| |
Notes:
svn path=/head/; revision=117813
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, there were two copies of telnet; a non-crypto version
that lived in the usual places, and a crypto version that lived in
crypto/telnet/. The latter was built in a broken manner somewhat akin
to other "contribified" sources. This meant that there were 4 telnets
competing with each other at build time - KerberosIV, Kerberos5,
plain-old-secure and base. KerberosIV is no longer in the running, but
the other three took it in turns to jump all over each other during a
"make buildworld".
As the crypto issue has been clarified, and crypto _calls_ are not
a problem, crypto/telnet has been repo-copied to contrib/telnet,
and with this commit, all telnets are now "contribified". The contrib
path was chosen to not destroy history in the repository, and differs
from other contrib/ entries in that it may be worked on as "normal"
BSD code. There is no dangerous crypto in these sources, only a
very weak system less strong than enigma(1).
Kerberos5 telnet and Secure telnet are now selected by using the usual
macros in /etc/make.conf, and the build process is unsurprising and
less treacherous.
Notes:
svn path=/head/; revision=117675
|
| |
|
|
|
|
|
| |
Reported by: jhay
Notes:
svn path=/head/; revision=90296
|
| |
|
|
|
|
|
|
| |
Also, add an "unifdef:" target, so that the telnet sources can
be remade from the crypto sources in src/crypto/telnet.
Notes:
svn path=/head/; revision=87147
|
| |
|
|
|
|
|
|
| |
Also remove conditional (AUTHENTICATION) code as we have never compiled
it here, and it is doubtful that it even works in this scenario.
Notes:
svn path=/head/; revision=81963
|
| |
|
|
|
|
|
| |
Approved by: markm
Notes:
svn path=/head/; revision=74928
|
| |
|
|
|
|
|
| |
- MAN[1-9] -> MAN.
Notes:
svn path=/head/; revision=74814
|
| |
|
|
| |
Notes:
svn path=/head/; revision=74529
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-inetd
-rshd
-rlogind
-telnetd
-rsh
-rlogin
Reviewed by: freebsd-arch, cvs-committers
Obtained from: KAME project
Notes:
svn path=/head/; revision=56590
|
| |
|
|
| |
Notes:
svn path=/head/; revision=50476
|
| |
|
|
|
|
|
|
| |
As this is the non-crypto version, remove the useless (commented out)
directives and macros.
Notes:
svn path=/head/; revision=29918
|
| |
|
|
| |
Notes:
svn path=/head/; revision=22989
|
| |
|
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
Notes:
svn path=/head/; revision=21673
|
| |
|
|
| |
Notes:
svn path=/head/; revision=18471
|
| |
|
|
| |
Notes:
svn path=/head/; revision=18050
|
| |
|
|
| |
Notes:
svn path=/head/; revision=2678
|
| |
|
|
|
|
|
|
|
| |
(If you do, you will have problems trying to telnet into a FreeBSD-2.0
box from a Sun, and I WANT TO DO THAT.)
Submitted by: Geoff
Notes:
svn path=/head/; revision=2517
|
| |
|
|
|
|
|
|
| |
Only crypt.c in libc remains.
Reviewed by: Geoff Rehmet
Notes:
svn path=/head/; revision=2054
|
| |
|
|
|
|
|
| |
Submitted by: jkh
Notes:
svn path=/head/; revision=2002
|
| |
|
|
|
|
|
| |
set up right yet.
Notes:
svn path=/head/; revision=1875
|
|
|
Notes:
svn path=/vendor/CSRG/dist/; revision=1592
|