From: "Gix, Brian" <brian.gix@intel.com>
To: Laczen JMS <laczenjms@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: meshctl fails on rpi 3
Date: Sun, 17 Sep 2017 16:50:44 +0000 [thread overview]
Message-ID: <7560B49A-22C4-4A62-AE3F-B1AFA4712B30@intel.com> (raw)
In-Reply-To: <CAFxSrVsZcJxkgAFL8yoSK9buoSzFJryNT18mGSRUUq17VPdOEg@mail.gmail.com>
Hi Jehudi,
Meshctl' crypto does depend on a lot of Kernel based crypto... pretty much everything except for the AES-CCM.
Sent from my iPhone
> On Sep 17, 2017, at 8:42 AM, Laczen JMS <laczenjms@gmail.com> wrote:
>
> After downloading and compiling bluez 5.47 on raspberry pi 3 (raspbian
> 2017-09-07), it is not possible to run meshctl on the raspberry pi.
> Meshctl fails at loading the prov_db.
>
> After some further testing I have found that the loading fails in the
> crypto functions at binding the AF_ALG in line 178 of crypto.c. Has
> this something to do with cryptographic modules being unavailable on
> the rpi 3?
>
> If so, what crypto module is required and what is the best way to add
> these modules ?
>
> Kind regards,
>
> Jehudi
> --
> 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-17 16:50 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 [this message]
2017-09-17 17:48 ` Luiz Augusto von Dentz
2017-09-18 8:38 ` Marcel Holtmann
2017-09-18 8:54 ` Zabel, Oliver
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=7560B49A-22C4-4A62-AE3F-B1AFA4712B30@intel.com \
--to=brian.gix@intel.com \
--cc=laczenjms@gmail.com \
--cc=linux-bluetooth@vger.kernel.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