summaryrefslogtreecommitdiff
path: root/usr.bin/bdes
AgeCommit message (Collapse)Author
2023-06-27remove double/tripple o in comments, where it likely was not added on purpose.andvar
2017-07-03Remove workaround for ancient HTML generation code.wiz
2016-02-01PR/50739: David Binderman: Check bounds before dereferencing.christos
2013-08-15Use more static and __dead.joerg
2013-08-11Passes WARNS=5, so don't set WARNS=3.dholland
2010-01-15Use .%U instead of .%O for URLs.joerg
2009-04-14Fix sign-compare issueslukem
2008-07-21Remove the \n and tabs from the __COPYRIGHT() strings.lukem
Tweak to use a consistent format.
2007-05-28Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on thetls
FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to various string and memory copy and set functions (as well as a few system calls and other miscellany) where known at function entry. RedHat has evidently built all "core system packages" with this option for some time. This option should be used at the top of Makefiles (or Makefile.inc where this is used for subdirectories) but after any setting of LIB. This is only useful for userland code, and cannot be used in libc or in any code which includes the libc internals, because it overrides certain libc functions with macros. Some effort has been made to make USE_FORT=yes work correctly for a full-system build by having the bsd.sys.mk logic disable the feature where it should not be used (libc, libssp iteself, the kernel) but no attempt has been made to build the entire system with USE_FORT and doing so will doubtless expose numerous bugs and misfeatures. Adjust the system build so that all programs and libraries that are setuid, directly handle network data (including serial comm data), perform authentication, or appear likely to have (or have a history of having) data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default, with the exception of libc, which cannot use USE_FORT and thus uses only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no per-directory or in a system build will disable if desired.
2005-01-12WARNS=3xtraeme
2004-10-30Use strtoul() for integer conversiondsl
2004-06-04Remove DISCLAIMER section, which is just part of the usual BSD licensewiz
(which is also in comments at the top of the file).
2004-06-04Convert SEE ALSO to use Rs/Re.wiz
2003-08-07Move UCB-licensed code from 4-clause to 3-clause licence.agc
Patches provided by Joel Baker in PR 22365, verified by myself.
2003-02-25.Nm does not need a dummy argument ("") before punctuation orwiz
for correct formatting of the SYNOPSIS any longer.
2002-09-30New sentence, new line.grant
2002-02-08Generate <>& symbolically. I'm avoiding .../dist/... directories for now.ross
2001-12-01mdocify. Needs a second pass for SEE ALSO section.wiz
XXX: Why do we have a 'standard' disclaimer big in its own section here?
2001-12-01Whitespace cleanup.wiz
2001-02-19convert to use getprogname()cgd
2000-10-04getopt(3) returns -1 not EOF.mjl
2000-06-16Make this build in a WARNS'ified environment.thorpej
2000-06-16Ressurect bdes(1).thorpej
2000-06-16The 4.4BSD bdes(1) program as existed in cryptosrc-us.thorpej
1999-07-12Nuke this from orbit. We don't have placeholders for any of the otherthorpej
only-in-crypto-us programs, so why should this be any different?
1998-01-09RCS Id Police.perry
1997-07-10don't xref obsolete crypt(1)mikel
1997-03-24- Makefile cleanupschristos
1996-10-19Fix PR1542: gross inaccuracies in bdes.1 Reviewed by Perrysommerfe
1996-10-18Use ${INSTALL}.thorpej
1995-07-24add dummy bdes script, which prints an error to stderr and exits with ancgd
error code. include manual page, because it's exportable. note in manual page that installed version doesn't actually work.