History log of /src/usr.bin/rfcomm_sppd/rfcomm_sppd.c |
Revision | | Date | Author | Comments |
1.17 |
| 10-Jan-2017 |
christos | need <sys/stat.h>
|
1.16 |
| 09-Dec-2013 |
wiz | branches: 1.16.8; Fix typo ("then" instead of "than")
|
1.15 |
| 18-Jul-2011 |
christos | branches: 1.15.2; 1.15.8; - use poll() instead of select() - make everything static - knf - consistently check for == -1 for syscall errors - isatty(fd) == tcgetattr(fd), don't do it twice - make error messages more consistent - use sig_atomic_t for variable set inside signal handler
|
1.14 |
| 18-Jul-2011 |
plunky | only modify the termios structure when tty_in is verifiably a terminal
|
1.13 |
| 03-Nov-2010 |
plunky | In server mode, relax the requirement to specify a channel number. If one is not given, attempt to allocate the first unused one.
|
1.12 |
| 24-Sep-2009 |
plunky | Add a new feature, allow to specify an alternative PSM value for the RFCOMM protocol to use in client or server mode. Also, handle the case where service search of the remote device returns non-standard PSM.
|
1.11 |
| 21-May-2009 |
plunky | use system provided MAX(a, b) macro instead of defining our own
|
1.10 |
| 12-May-2009 |
plunky | update rfcomm_sppd to use the new Service Discovery API
|
1.9 |
| 21-Jul-2008 |
lukem | branches: 1.9.6; Remove the \n and tabs from the __COPYRIGHT() strings. Tweak to use a consistent format.
|
1.8 |
| 21-Apr-2007 |
dsl | branches: 1.8.12; Fix 64bit build, strlen() doesn't return int.
|
1.7 |
| 21-Apr-2007 |
plunky | 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)
|
1.6 |
| 31-Mar-2007 |
plunky | fix warnings produced by -Wextra fix warnings produced by lack of const
|
1.5 |
| 08-Mar-2007 |
plunky | cut and paste error meant you could only use "-s <num>" as the last option on the commandline..
|
1.4 |
| 08-Mar-2007 |
plunky | only turn off input processing if it is on
|
1.3 |
| 01-Mar-2007 |
plunky | rework the -c and -s options to make them a bit more consistent.
when EOF is reached, we are done.
|
1.2 |
| 31-Jan-2007 |
plunky | 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.
|
1.1 |
| 19-Jun-2006 |
gdamore | branches: 1.1.4; 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.
|
1.1.4.3 |
| 19-Jul-2007 |
liamjfoy | Pull up following revision(s) (requested by plunky in ticket #744): sys/netbt/l2cap_lower.c: revision 1.6 sys/dev/bluetooth/btdev.h: revision 1.6 sys/netbt/sco_socket.c: revision 1.9 sys/netbt/rfcomm_upper.c: revision 1.3 sys/netbt/l2cap_socket.c: revision 1.7 sys/netbt/rfcomm_upper.c: revision 1.5 lib/libusbhid/usbhid.h: revision 1.5 sys/netbt/rfcomm_upper.c: revision 1.6 usr.sbin/btdevctl/btdevctl.c: revision 1.4 usr.sbin/btdevctl/btdevctl.h: revision 1.3 usr.sbin/btdevctl/btdevctl.8: revision 1.4 sys/netbt/rfcomm_session.c: revision 1.5 sys/netbt/hci.h: revision 1.10 usr.bin/rfcomm_sppd/rfcomm_sppd.c: revision 1.6 sys/netbt/hci_link.c: revision 1.11 usr.bin/rfcomm_sppd/rfcomm_sppd.c: revision 1.7 usr.bin/rfcomm_sppd/rfcomm_sppd.c: revision 1.8 sys/dev/bluetooth/btsco.c: revision 1.14 sys/netbt/rfcomm_session.c: revision 1.9 usr.sbin/btdevctl/sdp.c: revision 1.2 share/man/man9/bluetooth.9: revision 1.2 usr.sbin/btdevctl/sdp.c: revision 1.3 sys/dev/bluetooth/bthidev.c: revision 1.8 sys/netbt/l2cap.h: revision 1.4 sys/netbt/rfcomm.h: revision 1.3 sys/netbt/l2cap.h: revision 1.5 sys/netbt/l2cap_misc.c: revision 1.3 share/man/man4/bluetooth.4: revision 1.5 lib/libusbhid/usbhid.3: revision 1.11 sys/netbt/bluetooth.h: revision 1.5 share/man/man4/bthidev.4: revision 1.8 sys/netbt/rfcomm_dlc.c: revision 1.3 usr.sbin/btdevctl/print.c: revision 1.8 sys/netbt/rfcomm_socket.c: revision 1.7 sys/netbt/l2cap_signal.c: revision 1.4 sys/netbt/l2cap_signal.c: revision 1.5 sys/netbt/l2cap_signal.c: revision 1.7 sys/netbt/hci_event.c: revision 1.6 usr.bin/rfcomm_sppd/rfcomm_sppd.1: revision 1.5 sys/netbt/l2cap_upper.c: revision 1.3 sys/netbt/l2cap_lower.c: revision 1.2 usr.sbin/btdevctl/db.c: revision 1.3 sys/netbt/l2cap_upper.c: revision 1.6 lib/libusbhid/descr.c: revision 1.5 sys/netbt/l2cap_upper.c: revision 1.7 sys/netbt/l2cap_lower.c: revision 1.4 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) - ALSO INCLUDES OTHER MINOR FIXES
|
1.1.4.2 |
| 26-Mar-2007 |
jdc | branches: 1.1.4.2.2; Pull up revisions 1.4 and 1.5 (requested by plunky in ticket #517).
only turn off input processing if it is on
cut and paste error meant you could only use "-s <num>" as the last option on the commandline..
|
1.1.4.1 |
| 04-Mar-2007 |
bouyer | Pull up following revision(s) (requested by plunky in ticket #487): usr.bin/rfcomm_sppd/rfcomm_sppd.c: revisions 1.2-1.3 usr.bin/rfcomm_sppd/rfcomm_sppd.1: revisions 1.2-1.4 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.
|
1.1.4.2.2.1 |
| 03-Sep-2007 |
wrstuden | Sync w/ NetBSD-4-RC_1
|
1.8.12.1 |
| 18-Sep-2008 |
wrstuden | Sync with wrstuden-revivesa-base-2.
|
1.9.6.1 |
| 13-May-2009 |
jym | Sync with HEAD.
Third (and last) commit. See http://mail-index.netbsd.org/source-changes/2009/05/13/msg221222.html
|
1.15.8.1 |
| 20-Aug-2014 |
tls | Rebase to HEAD as of a few days ago.
|
1.15.2.1 |
| 22-May-2014 |
yamt | sync with head.
for a reference, the tree before this commit was tagged as yamt-pagecache-tag8.
this commit was splitted into small chunks to avoid a limitation of cvs. ("Protocol error: too many arguments")
|
1.16.8.1 |
| 20-Mar-2017 |
pgoyette | Sync with HEAD
|