ussp-push is a Linux software that enables users to transfer objects over Bluetooth using the OBEX protocol.
The ussp-push application is a Bluetooth object pusher that is specifically designed for Linux, using the BlueZ Bluetooth stack. The initial implementation of ussp-push required explicit binding to RFCOMM channels before usage, which made it difficult to use. However, with the addition of Bluetooth name resolution and direct access to remote Bluetooth listening channels, the syntax for ussp-push has greatly improved.
The current syntax supported by ussp-push is:
$ ussp-push [--dev DEVID] {DEVICE, BTADDR@BTCHAN} LFILE RFILE
Where:
- DEVID: This is the HCI device ID, and it's only valid if the BTADDR@BTCHAN syntax is deployed.
- DEVICE: This refers to the RFCOMM device file, such as /dev/rfcomm0.
- BTADDR@BTCHAN: This is the Bluetooth address and channel of the remote OBEX listener. The BTADDR can either be a Bluetooth address or a Bluetooth device name.
- LFILE: This is the local file path.
- RFILE: This is the remote file name.
One of the significant improvements included in this release is the fix for an unaligned read bug that was revealed in alignment-critical platforms.
The current syntax supported by ussp-push is:
$ ussp-push [--dev DEVID] {DEVICE, BTADDR@BTCHAN} LFILE RFILE
Where:
- DEVID: This is the HCI device ID, and it's only valid if the BTADDR@BTCHAN syntax is deployed.
- DEVICE: This refers to the RFCOMM device file, such as /dev/rfcomm0.
- BTADDR@BTCHAN: This is the Bluetooth address and channel of the remote OBEX listener. The BTADDR can either be a Bluetooth address or a Bluetooth device name.
- LFILE: This is the local file path.
- RFILE: This is the remote file name.
One of the significant improvements included in this release is the fix for an unaligned read bug that was revealed in alignment-critical platforms.
What's New
Version 0.11: N/A