User's Manual

SECURITY

Introduction

Each service that the server provides can be configured to require the following:

 Authorization: the server operator must acknowledge all

connection attempts before a connection is established.

 Authentication: the server requires a Personal Identification

Number code (PIN, also referred to as a “passkey”) or a Link Key

before a connection is established.

 Encryption: all data sent between the Bluetooth client and

Bluetooth server is encrypted. The encryption key is based on the

Authentication Link Key. Encryption requires that Authentication

be enabled.

All three – Authorization, Authentication, and Encryption – are disabled by default. Devices can

also be paired, a process that eliminates the need to enter a PIN code each time access is

attempted.

Authentication

Authentication is used to verify identity. It requires a passkey or Link Key from the remote device.

When a remote device attempts access to a unit, a visual and/or audio warning notifies the local

operator of the invitation.

The local operator can open a dialog box that provides:

1. The user-friendly name of the device attempting access.

2. A place for the local operator to enter a Bluetooth passkey.

The operator of the remote system must then enter the identical passkey. If no passkey is

supplied or if the notification is ignored after a preset timeout, access will be denied. In cases

wherein devices are paired, those devices automatically exchange a Link Key and authentication

is carried out without operator intervention.

Authorization

Authorization is yes-or-no security. When a remote device attempts to connect, a visual and/or

audio warning alerts the server operator.

The server operator then responds by clicking the Bluetooth Tray icon in the Windows system

tray to open a dialog box that displays:

1. The user-friendly name of the device attempting to connect.

2. The local service to which the remote device is attempting to

connect.