Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: [PATCH BlueZ] mesh: test AEAD at startup to check kernel support
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <20190830182316.fo3nmzfvzk55rhnj@kynes>
Date:   Fri, 30 Aug 2019 20:52:26 +0200
Cc:     Brian Gix <brian.gix@intel.com>, linux-bluetooth@vger.kernel.org,
        inga.stotland@intel.com
Content-Transfer-Encoding: 8BIT
Message-Id: <3389022D-8306-4276-A715-C2906EB0D91F@holtmann.org>
References: <20190830173902.19953-1-brian.gix@intel.com>
 <20190830182316.fo3nmzfvzk55rhnj@kynes>
To:     =?utf-8?Q?Micha=C5=82_Lowas-Rzechonek?= 
        <michal.lowas-rzechonek@silvair.com>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Michal,

>> One time test at startup to ensure either kernel version v4.9 or later,
>> *or* that required AES-CCM support has been back-ported. If support not
>> there, daemon will run without providing D-Bus service or attaching to
>> controllers (prevents systemd thrashing).
> 
> By the way - I have a patch that implements all required cryptographic
> operations using libcrypto, enabled by ./configure --with-openssl
> (disabled by default).
> 
> I know that last time we've talked about this, the consensus was that the
> vendor should patch meshd to work on older kernels, so we did exactly
> that - but maybe having this available in the mainline would be
> interesting?

we are not using anything from OpenSSL. That is a rabbit hole you are not getting back out of.

Regards

Marcel