From: Marcel Holtmann <marcel@holtmann.org>
To: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
Cc: Brian Gix <brian.gix@intel.com>,
linux-bluetooth@vger.kernel.org, inga.stotland@intel.com
Subject: Re: [PATCH BlueZ] mesh: test AEAD at startup to check kernel support
Date: Fri, 30 Aug 2019 20:52:26 +0200 [thread overview]
Message-ID: <3389022D-8306-4276-A715-C2906EB0D91F@holtmann.org> (raw)
In-Reply-To: <20190830182316.fo3nmzfvzk55rhnj@kynes>
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
prev parent reply other threads:[~2019-08-30 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 17:39 [PATCH BlueZ] mesh: test AEAD at startup to check kernel support Brian Gix
2019-08-30 17:55 ` Mat Martineau
2019-08-30 18:23 ` Michał Lowas-Rzechonek
2019-08-30 18:38 ` Gix, Brian
2019-08-30 18:43 ` michal.lowas-rzechonek
2019-08-30 18:52 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3389022D-8306-4276-A715-C2906EB0D91F@holtmann.org \
--to=marcel@holtmann.org \
--cc=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).