All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hammami Omar <omar18hammami@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] SSH server starts too late
Date: Tue, 3 Mar 2020 13:33:58 +0100	[thread overview]
Message-ID: <CAGSpp9n8KTJvuAXWsVRUD09fovskkknHTBR57k87xo8LK2ZAhg@mail.gmail.com> (raw)
In-Reply-To: <CAGSpp9ktPHnTeqQ2VkVW4D31QKMb68gBATkHo3PaW9NemeY8nQ@mail.gmail.com>

Hello,

My problem is not resolved yet.
In fact, I have known that the libopenssl *1.1.1d* use getrandom function
in blocking mode.
So to disable this I have applied the modification below in
*crypto/rand/rand_unix.c* . But my problem is not resolved. In fact, my ssh
server starts too late (after ~2 minutes).

patch :
*# if defined(__linux) && defined(__NR_getrandom) *

* - return syscall(__NR_getrandom, buf, buflen, 0); *
*  +   return syscall(__NR_getrandom, buf, buflen, * *GRND_NONBLOCK* *);*

Did I miss something ?

In fact, I applied this modification because I saw that my ssh server
started only if the* nonblocking pool was initialized*.

Is it possible that  "*OPENSSL_RAND_SEED_GETRANDOM"* is not defined ?


*Note :*
I am using the openssh version* 8.1p1*

Kind regards,
Omar

Le ven. 21 f?vr. 2020 ? 19:30, Hammami Omar <omar18hammami@gmail.com> a
?crit :

> hello Grant,
>
> No, I have always the same "/var/ssh_host_rsa_key"
> The haveged script was started, I have very high value of entropy (2332)
> and the sshd process started too late.
>
>
> Le ven. 21 f?vr. 2020 ? 19:10, Grant Edwards <grant.b.edwards@gmail.com>
> a ?crit :
>
>> On 2020-02-21, Hammami Omar <omar18hammami@gmail.com> wrote:
>>
>> > By too late, I mean that my ssh server starts ~20 seconds later
>> comparing
>> > to the normal  (Old buildroot version in my case).
>>
>> Does it generate a new host key each time it starts?
>>
>> --
>> Grant Edwards               grant.b.edwards        Yow! Is a tattoo real,
>> like
>>                                   at               a curb or a battleship?
>>                               gmail.com            Or are we suffering in
>>                                                    Safeway?
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200303/67072457/attachment.html>

  reply	other threads:[~2020-03-03 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  9:13 [Buildroot] SSH server starts too late Hammami Omar
2020-02-21 10:19 ` Peter Seiderer
2020-02-21 14:50   ` Hammami Omar
2020-02-21 16:16     ` Hammami Omar
2020-02-21 18:08     ` Grant Edwards
2020-02-21 18:30       ` Hammami Omar
2020-03-03 12:33         ` Hammami Omar [this message]
     [not found] <mailman.11.1582286403.41897.buildroot@busybox.net>
2020-02-21 12:51 ` Andreas Ziegler
2020-02-24  9:29   ` Hammami Omar
     [not found]     ` <1d91f38acaeecb790f5a44d104ae0ca1@umbiko.net>
2020-02-24 13:07       ` Andreas Ziegler
     [not found]       ` <CAGSpp9ng2yxCK=RZeq1Z_Bce4pwij9FQED23SpGuvjqm5awHhg@mail.gmail.com>
2020-02-24 13:22         ` Andreas Ziegler
2020-02-24 14:07           ` Hammami Omar
2020-02-24 15:16             ` Hammami Omar

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=CAGSpp9n8KTJvuAXWsVRUD09fovskkknHTBR57k87xo8LK2ZAhg@mail.gmail.com \
    --to=omar18hammami@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.