Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [PATCH v3] Bluetooth: Add HCI_AUTO_CONN_DIRECT_REPORT_IND From: Marcel Holtmann In-Reply-To: Date: Mon, 29 Sep 2014 16:54:01 +0200 Cc: linux-bluetooth@vger.kernel.org Message-Id: References: <1411746855-9936-1-git-send-email-fons@spotify.com> <24D2CD11-D43B-4F53-8A7C-175934A54C87@holtmann.org> <1D7AEE8B-51DB-4A6D-8EBA-3EC81760224E@holtmann.org> To: Alfonso Acosta Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Alfonso, >> if it can not store its LTK, then why doesn't it use a key hierarchy (as defined in the Bluetooth specification) so that it can restore its keys after reboot. If it remembers its Bluetooth address, then it could clearly remember a single master key. >> >> But seriously, if you can remember your BD_ADDR, then you might want to remember your LTK as well. Just a hint here. > > > Thanks for the hint, I wasn't familiar with "key hierarchies". you should really only use them if your device has no persistent storage. If you have a choice, get a device that has persistent storage. Since generating a random LTK for each device (instead of deriving it from a key hierarchy) is of course more secure. Regards Marcel