[Bug 593227] [NEW] feature request: add a root-path parameter

[Alkis Georgopoulos]

Στις 14-06-2010, ημέρα Δευ, και ώρα 20:35 +0000, ο/η Wouter Verhelst
έγραψε:
> NBD has a "virtual host" feature that allows you to change the served
> file based on (part of) the IP address of the client that's
> connecting.

That would indeed work for some use cases, but unfortunately fixed IP
addresses would be required, which isn't always an option.

> I'd prefer that the client would be able to specify a name of an
> export, with the server using the section name in the config file as
> the name of the export, rather than having the ability to specify a
> path; the latter would have some security ramifications that I'd
> prefer not to deal with.

I was thinking something like /etc/exports, with one entry per line,
which would make it easier for postinst/postrm scripts to handle. In
essence the two methods are the same except that the whole "section" is
in one line, and the full path is used as the "section name" - I can't
see any differences security-wise. But sure, the configuration file
format (or config.d directory if implemented) is not an issue at all.

Thank you very much,
Alkis

-- 
feature request: add a root-path parameter
https://bugs.launchpad.net/bugs/593227
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.

Status in “ltsp” package in Ubuntu: New
Status in “nbd” package in Ubuntu: New

Bug description:
Currently nbd-server and nbd-client communicate using a different port for each image. So if e.g. an LTSP admin wants to use a chroot for nvidia-based clients and a chroot for the rest of his clients, he'd need to use two ports. And he wanted nbd swapping a third port would be needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
 * A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
 * A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.