All of lore.kernel.org
 help / color / mirror / Atom feed
From: rob.r374 at gmail.com <rob.r374@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to safely connect to remote embedded systems (mostly behind Firewalls) ?
Date: Sun, 6 Dec 2020 12:31:05 +0100	[thread overview]
Message-ID: <011701d6cbc3$49d7f7c0$dd87e740$@gmail.com> (raw)

Hello,

 

I'm preparing buildroot based distribution for ARM Cortex M7
(noMMU,STM32F769 DISCO board).

I'd like to implement possibility to remotely connect from distant server,
to check and supervise the system.

I think that >reverse shell< is what I'm looking for (so remote system on
some trigger connects safely to some distant server, from which I can work
in shell). I guess dropbear that is already present in my system could be
used for this.

 

Is this solution safe and how can be implemented efficiently on these
resource constrained devices ?

 

Thanks,

Regards,

Rob.



-- 
Ta e-po?ta je bila pregledana z Avast protivirusnim programom.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20201206/d6666edf/attachment.html>

                 reply	other threads:[~2020-12-06 11:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='011701d6cbc3$49d7f7c0$dd87e740$@gmail.com' \
    --to=rob.r374@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.