diff options
| author | Arman Uguray <armansito@chromium.org> | 2015-02-27 20:42:51 -0800 |
|---|---|---|
| committer | Arman Uguray <armansito@chromium.org> | 2015-02-27 20:45:00 -0800 |
| commit | cc6296194d41aa1480287a7173137437630a167c (patch) | |
| tree | 7c20f000892eba81e1ca1068cf0e0db71275ea71 | |
| parent | 373ee416c36bd6a2dea786212fe914a425156829 (diff) | |
| download | bluez-cc6296194d41aa1480287a7173137437630a167c.tar.gz | |
TODO: Added item about PF_ALG error
Added GATT related TODO item to gracefully handle signed writes and
bt_att initialization if the CONFIG_CRYPTO_USER_API modules that are
necessary for bt_crypto are not enabled in the system.
| -rw-r--r-- | TODO | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -189,6 +189,22 @@ ATT/GATT (new shared stack) Priority: Medium Complexity: C1 +- The recently added support for ATT signed writes requires the following kernel + modules to be enabled: + + CONFIG_CRYPTO_USER_API + CONFIG_CRYPTO_USER_API_HASH + CONFIG_CRYPTO_USER_API_SKCIPHER + + Currently, if these are not enabled, bt_att_new silently returns NULL. We + should handle this more gracefully by not supporting signed writes if we can't + initialize bt_crypto while succeeding bt_att initialization regardless. + + This behavior should be documented in the README. + + Priority: High + Complexity: C1 + ATT/GATT (old/outdated) ======================= |