//device/bluetooth support for attribute properties and permissions.

device/bluetooth/bluetooth_gatt_characteristic.h

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef DEVICE_BLUETOOTH_BLUETOOTH_GATT_CHARACTERISTIC_H_
 #define DEVICE_BLUETOOTH_BLUETOOTH_GATT_CHARACTERISTIC_H_
 
 #include <stdint.h>
 #include <string>
 
@@ skipping 28 matching lines @@
     PROPERTY_NONE = 0,
     PROPERTY_BROADCAST = 1 << 0,
     PROPERTY_READ = 1 << 1,
     PROPERTY_WRITE_WITHOUT_RESPONSE = 1 << 2,
     PROPERTY_WRITE = 1 << 3,
     PROPERTY_NOTIFY = 1 << 4,
     PROPERTY_INDICATE = 1 << 5,
     PROPERTY_AUTHENTICATED_SIGNED_WRITES = 1 << 6,
     PROPERTY_EXTENDED_PROPERTIES = 1 << 7,
     PROPERTY_RELIABLE_WRITE = 1 << 8,
-    PROPERTY_WRITABLE_AUXILIARIES = 1 << 9
+    PROPERTY_WRITABLE_AUXILIARIES = 1 << 9,
+    PROPERTY_READ_ENCRYPTED = 1 << 10,
+    PROPERTY_WRITE_ENCRYPTED = 1 << 11,
+    PROPERTY_READ_ENCRYPTED_AUTHENTICATED = 1 << 12,
+    PROPERTY_WRITE_ENCRYPTED_AUTHENTICATED = 1 << 13,
+    NUM_PROPERTY = 1 << 14,
   };
   typedef uint32_t Properties;
 
   // Values representing read, write, and encryption permissions for a
   // characteristic's value. While attribute permissions for all GATT
   // definitions have been set by the Bluetooth specification, characteristic
   // value permissions are left up to the higher-level profile.
   //
   // Attribute permissions are distinct from the characteristic properties. For
   // example, a characteristic may have the property |PROPERTY_READ| to make
   // clients know that it is possible to read the characteristic value and have
   // the permission |PERMISSION_READ_ENCRYPTED| to require a secure connection.
   // It is up to the application to properly specify the permissions and
   // properties for a local characteristic.
+  // TODO(rkc): Currently BlueZ infers permissions for characteristics from
+  // the properties. Once this is fixed, we will start sending the permissions
+  // for characteristics to BlueZ. Till then permissions for characteristics
+  // are unimplemented.
   enum Permission {
     PERMISSION_NONE = 0,
     PERMISSION_READ = 1 << 0,
     PERMISSION_WRITE = 1 << 1,
     PERMISSION_READ_ENCRYPTED = 1 << 2,
-    PERMISSION_WRITE_ENCRYPTED = 1 << 3
+    PERMISSION_WRITE_ENCRYPTED = 1 << 3,
+    PERMISSION_READ_ENCRYPTED_AUTHENTICATED = 1 << 4,
+    PERMISSION_WRITE_ENCRYPTED_AUTHENTICATED = 1 << 5,
+    NUM_PERMISSION = 1 << 6,
   };
   typedef uint32_t Permissions;
 
   // The ErrorCallback is used by methods to asynchronously report errors.
   typedef base::Callback<void(BluetoothGattService::GattErrorCode)>
       ErrorCallback;
 
   // Identifier used to uniquely identify a GATT characteristic object. This is
   // different from the characteristic UUID: while multiple characteristics with
   // the same UUID can exist on a Bluetooth device, the identifier returned from
@@ skipping 14 matching lines @@
   BluetoothGattCharacteristic();
   virtual ~BluetoothGattCharacteristic();
 
  private:
   DISALLOW_COPY_AND_ASSIGN(BluetoothGattCharacteristic);
 };
 
 }  // namespace device
 
 #endif  // DEVICE_BLUETOOTH_BLUETOOTH_GATT_CHARACTERISTIC_H_