linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Alexandre Augusto <alexandre.a.giron@gmail.com>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: Entropy source based on the RSSI
Date: Thu, 15 Oct 2020 16:00:09 -0700	[thread overview]
Message-ID: <CABBYNZKP45JDj7dBAADVN7+1vpLCEcFy2y62yfGE0c1gGG5fjA@mail.gmail.com> (raw)
In-Reply-To: <CABLzjm8S1J5MRhrwFu1pbX9fub7X5nXmYRWmtRsmVRObeJOCbw@mail.gmail.com>

Ola Alexandre,

Que coincidência ver alguem da UTFPR por aqui, fiz meu mestrado ai em
2003, muito legal o seu trabalho. So por curiosidade, voce chegou a
usar o BT_HCI_CMD_LE_RAND como fonte de entropia? No Zephyr
(https://www.zephyrproject.org/) agente usa bastante porque o
controlador pode usar o sinal de interferência direto da camada do
radio, abaixo da interface HCI, e segundo o pessoal da Nordic tem uma
qualidade bem maior do que por exemplo RSSI porque nao depende da
quantidade de dispositivos em volta.

On Thu, Oct 15, 2020 at 2:59 PM Alexandre Augusto
<alexandre.a.giron@gmail.com> wrote:
>
> Hello,
>
> based on the motivation that IoT devices do not have many entropy
> sources available, and also on the fact that trusting in a single
> source may be risky, I have researched some additional ways to collect
> randomness for the device, using bluetooth technology for that
> purpose.
>
> For those who are interested in:
>
> Github: https://github.com/AAGiron/Bluerandom
> Presentation: https://www.youtube.com/watch?v=iAKaKAmqCFo
>
> I also want to say thanks in advance to Emil Lenngren for his valuable
> comments, here in this mailing list (back in 2019), and also to the
> Bluez community.
>
> --
> Alexandre Augusto Giron



-- 
Luiz Augusto von Dentz

  reply	other threads:[~2020-10-15 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 18:34 Entropy source based on the RSSI Alexandre Augusto
2020-10-15 23:00 ` Luiz Augusto von Dentz [this message]
2020-10-20 18:38 ` Marcel Holtmann
2020-10-20 18:57   ` Alexandre Augusto
2020-10-20 19:19   ` Alexandre Augusto

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=CABBYNZKP45JDj7dBAADVN7+1vpLCEcFy2y62yfGE0c1gGG5fjA@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=alexandre.a.giron@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;
as well as URLs for NNTP newsgroup(s).