From: "debbug@Think-Future.de" <debbug@Think-Future.de>
To: Manfred Haertel <Manfred.Haertel@rz-online.de>
Cc: grub-devel@gnu.org
Subject: Re: SSH into GRUB2
Date: Sat, 28 Dec 2019 13:10:04 +0100 [thread overview]
Message-ID: <20191228121004.GL27729@think-future.de> (raw)
In-Reply-To: <f7cbe83a-4d28-d4d9-71ac-03c3bf9feaa9@think-future.de>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Hello Manfred,
Thank you for your quick reply.
That's good news.
Any chance you could provide your code for reference?
Happy holidays,
Nils
On 2019-12-27 05:56:33, Manfred Haertel wrote:
>DebBug schrieb:
>
>>Is there any support for or are there any intentions to support
>>SSHing into GRUB2?
>>
>>I realize this would require a network stack to be integrated. Is
>>this feasible with reasonable effort? Would it be accepted at all?
>
>grub2 already contains a complete and working TCP/IP stack. The only
>thing which may be missing is a card driver for the environment it is
>running on.
>
>I once wrote a card driver for the Xen virtual network card and a
>Telnet implementation, just to educate myself. It is not perfect (nor
>secure), but it works. So it should not be impossible to implement ssh
>support.
>
>--
>Manfred Härtel, DB3HM mailto:Manfred.Haertel@rz-online.de
> http://rz-home.de/mhaertel
>
>_______________________________________________
>Grub-devel mailing list
>Grub-devel@gnu.org
>https://lists.gnu.org/mailman/listinfo/grub-devel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2019-12-28 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 0:07 SSH into GRUB2 DebBug
2019-12-27 4:56 ` Manfred Haertel
[not found] ` <f7cbe83a-4d28-d4d9-71ac-03c3bf9feaa9@think-future.de>
2019-12-28 12:10 ` debbug [this message]
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=20191228121004.GL27729@think-future.de \
--to=debbug@think-future.de \
--cc=Manfred.Haertel@rz-online.de \
--cc=grub-devel@gnu.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 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.