From: Stas Sergeev <stsp@list.ru>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Mateusz Viste <mateusz@viste-family.net>,
linux-msdos@vger.kernel.org,
dosemu-devel <dosemu-devel@lists.sourceforge.net>
Subject: Re: DOSemu networking made easy
Date: Tue, 25 Jun 2013 11:13:15 +0400 [thread overview]
Message-ID: <51C9430B.3080300@list.ru> (raw)
In-Reply-To: <87a9mfdqid.fsf@xmission.com>
25.06.2013 03:43, Eric W. Biederman пишет:
> At a very basic level I don't know if it is wise to make it easy to
> open up old unmaintained dos executables to the public internet.
According to wikipedia:
https://en.wikipedia.org/wiki/Slirp#Limitations
slirp cannot accept the incoming connections, and therefore
gives as much of a protection as the NAT does.
But I really can't follow their (wikipedia) logic: at least if the
port is not already in use, why can't slirp open it to listen for
the incoming connections? They claim you need a port forwarding
for that.
> maintenance dead end. If slirp updates can be pulled from qemu I don't
> imagine there will be any maintenance problems.
Well you probably know how "often" the dosemu releases
are made: not much more frequently than the ones of slirp. :)
So if there be some updates on slirp, even if someone will pull
them into dosemu git quickly, they have zero chances to reach
the user within 10 years or more, so this is not the best solution. :))
--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" 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:[~2013-06-25 7:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 11:36 DOSemu networking made easy Mateusz Viste
2013-06-24 13:23 ` Stas Sergeev
2013-06-24 13:50 ` Mateusz Viste
2013-06-24 15:00 ` Stas Sergeev
2013-06-24 15:38 ` Mateusz Viste
2013-06-24 16:12 ` Stas Sergeev
2013-06-24 19:58 ` Eric W. Biederman
2013-06-24 20:42 ` Stas Sergeev
2013-06-24 22:04 ` Mateusz Viste
2013-06-25 7:03 ` Stas Sergeev
2013-06-25 7:33 ` Mateusz Viste
2013-06-25 8:27 ` Eric W. Biederman
[not found] ` <87zjue8ujo.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2013-06-25 11:43 ` Stas Sergeev
2013-06-25 9:48 ` Stas Sergeev
2013-06-25 11:16 ` Eric W. Biederman
2013-06-25 13:30 ` Mateusz Viste
2013-06-24 21:47 ` Mateusz Viste
2013-06-24 23:43 ` Eric W. Biederman
2013-06-25 6:49 ` Mateusz Viste
[not found] ` <8fbd00db-16cc-4fd2-8135-0c3c99fcc3a6-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-06-25 7:47 ` Eric W. Biederman
2013-06-25 7:13 ` Stas Sergeev [this message]
2013-06-25 7:57 ` Eric W. Biederman
2013-06-25 9:45 ` Stas Sergeev
2013-06-24 14:40 ` Mateusz Viste
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=51C9430B.3080300@list.ru \
--to=stsp@list.ru \
--cc=dosemu-devel@lists.sourceforge.net \
--cc=ebiederm@xmission.com \
--cc=linux-msdos@vger.kernel.org \
--cc=mateusz@viste-family.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox