From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: IPX without suidroot
Date: Fri, 02 Aug 2002 21:19:38 +0400 [thread overview]
Message-ID: <3D4ABF2A.3040305@yahoo.com> (raw)
Hello.
Grigory Batalov wrote:
> IPX: GetLocalTarget for network cb971126
> IPX: Received RIP information for network 261197cb
This time it finally received
RIP, good!
> IPX: Failure -2 adding route <261197cb through 00000002:000102877d41>
Ouch, and this time it comes to
the place which really requires
root (CAP_NET_ADMIN capability)...
Is this possible to set that route
manually (being root)?
Maybe something like
ipx_route add 261197cb 02 102877d41
will do the trick?
But even that may not help.
Currently dosemu doesn't check if
the route exists *before* adding
it, so it still may fail.
To do the check /proc/net/ipx_route
must be parsed, but this is not
what I can do without an ability
to test the changes...
Anyway there were several bugs
discovered, so I'd like to bring
that investigation to some conclusion.
So if adding route manually doesn't
help, could you please (only for testing
purposes) remove the
if (!capable(CAP_NET_ADMIN))
return -EPERM;
from kernel's af_ipx.c:2403
(ipx_ioctl() ).
I want to know if my patch
really works and if there is
nothing more standing in the way...
next reply other threads:[~2002-08-02 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 17:19 Stas Sergeev [this message]
2002-08-02 21:43 ` IPX without suidroot Grigory Batalov
2002-08-05 5:47 ` Grigory Batalov
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 14:37 Stas Sergeev
2002-08-02 15:52 ` Grigory Batalov
2002-08-02 12:38 Stas Sergeev
2002-08-02 13:47 ` Grigory Batalov
2002-08-01 14:02 Stas Sergeev
2002-08-02 10:52 ` Grigory Batalov
2002-08-01 10:36 Grigory Batalov
2002-08-01 11:58 ` Reinhard Karcher
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=3D4ABF2A.3040305@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.org \
--cc=stas.orel@mailcity.com \
/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