netdev - Re: non-root, non-real network manipulation for netconf testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 Jun 2008 11:05:14 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	netdev discussion list <netdev@...r.kernel.org>,
	netconf developers list <netconf-devel@...ts.alioth.debian.org>
Subject: Re: non-root, non-real network manipulation for netconf testing

martin f krafft wrote:
> Dear networking wizards,
> 
> This is a bit of a self-reflexive mail, but I hope some of you might
> have some input...
> 
> In writing netconf[0], we are having a bit of a problem with the
> test suite, since many of netconf's operations require root rights
> (e.g. interface manipulation with /bin/ip). In addition, a test
> suite manipulating the network configuration of the running machine
> is not really something I feel comfortable with.
> 
> 0. http://netconf.alioth.debian.org
> 
> So I am trying to come up with alternative plans, of which there are
> three:
> 
> 1. do not fail tests that need root rights when run as non-root
> 2. set up a VDE network (which still requires root rights)
> 3. write a mock /bin/ip which pretends to be doing what it'd be doing
[...]

Have you considering running the tests in User-Mode Linux or some
other kind of virtualised environment?

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html