From: "Zabel, Oliver" <oliverzabel@gmx.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Brian Gix <brian.gix@intel.com>, Laczen JMS <laczenjms@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: meshctl fails on rpi 3
Date: Mon, 18 Sep 2017 10:54:27 +0200 [thread overview]
Message-ID: <6C104080-2AFC-4D11-84EC-862CF31BC796@gmx.de> (raw)
In-Reply-To: <EF2EC730-AB08-460A-8545-653982057FBC@holtmann.org>
Hi,
what is then the procedure to get crypto/meshctl running on rpi3/pi zero w?
Thanks!
Von meinem iPhone gesendet
> Am 18.09.2017 um 10:38 schrieb Marcel Holtmann <marcel@holtmann.org>:
>=20
> Hi Luiz,
>=20
>>> Meshctl' crypto does depend on a lot of Kernel based crypto... pretty mu=
ch everything except for the AES-CCM.
>>=20
>> We might want to update
>> https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/doc/test-runner.t=
xt
>> if that is not covering the mesh crypto.
>=20
> I would also prefer that we start using AES-CCM from the kernel. Someone s=
hould take up that task and also use src/shared/crypto.c for it. We should e=
nsure that we use a single place for all the crypto helpers.
>=20
> Regards
>=20
> Marcel
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"=
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-09-18 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 15:41 meshctl fails on rpi 3 Laczen JMS
2017-09-17 16:50 ` Gix, Brian
2017-09-17 17:48 ` Luiz Augusto von Dentz
2017-09-18 8:38 ` Marcel Holtmann
2017-09-18 8:54 ` Zabel, Oliver [this message]
2017-09-18 10:50 ` Tudor Ambarus
2017-09-18 19:48 ` Laczen JMS
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=6C104080-2AFC-4D11-84EC-862CF31BC796@gmx.de \
--to=oliverzabel@gmx.de \
--cc=brian.gix@intel.com \
--cc=laczenjms@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
/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