Commit Graph

11 Commits

Author SHA1 Message Date
wiz 8ed18604e6 Drop trailing whitespace. Fix typo and casing. 2007-12-02 20:41:40 +00:00
tls 4147a3c54a Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the
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.
2007-05-28 12:06:17 +00:00
dsl 858e924206 Fix 64bit build, strlen() doesn't return int. 2007-04-21 10:39:30 +00:00
plunky f5db72e7b7 Add 'service level' security for L2CAP and RFCOMM connections, following
the Linux (BlueZ) API.

    - L2CAP or RFCOMM connections can require the baseband radio link
    mode be any of:
	authenticated (devices are paired)
	encrypted (implies authentication)
	secured (encryption, plus generate new link key)

    - for sockets, the mode is set using setsockopt(2) and the socket
    connection will be aborted if the mode change fails.

    - mode settings will be applied during connection establishment, and
    for safety, we enter a wait state and will only proceed when the mode
    settings are successfuly set.

    - It is possible to change the mode on already open connections, but
    not possible to guarantee that data already queued (from either end)
    will not be delivered. (this is a feature, not a bug)

    - bthidev(4) and rfcomm_sppd(1) support "auth", "encrypt" and
    "secure" options

    - btdevctl(8) by default enables "auth" for HIDs, and "encrypt" for
    keyboards (which are required to support it)
2007-04-21 06:15:22 +00:00
plunky 89f52265ce fix warnings produced by -Wextra
fix warnings produced by lack of const
2007-03-31 07:14:44 +00:00
plunky ca0b33b2ff cut and paste error meant you could only use "-s <num>" as the last
option on the commandline..
2007-03-08 19:13:14 +00:00
plunky e55e3c248c only turn off input processing if it is on 2007-03-08 19:10:49 +00:00
plunky d7e75bcc12 rework the -c and -s options to make them a bit more consistent.
when EOF is reached, we are done.
2007-03-01 21:44:30 +00:00
wiz c8db62531e Sort sections. New sentence, new line. 2007-02-01 06:54:40 +00:00
plunky defc1075ef This comprises a rewrite, which
- adds a server mode for incoming bluetooth connections
	- does not cfmakeraw the slave tty as this caused problems
	- does not hold open the slave tty as this prevented multiple opens
	- modifies the termios for stdio so that this can be used directly
	  by a user.
2007-01-31 08:12:21 +00:00
gdamore a5c89047c0 Initial import of bluetooth stack on behalf of Iain Hibbert. (plunky@,
NetBSD Foundation Membership still pending.)  This stack was written by
Iain under sponsorship from Itronix Inc.

The stack includes support for rfcomm networking (networking via your
bluetooth enabled cell phone), hid devices (keyboards/mice), and headsets.

Drivers for both PCMCIA and USB bluetooth controllers are included.
2006-06-19 15:44:33 +00:00