linux-kernel - Re: [PATCH] nbd: show nbd client pid in sysfs

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:	Sun, 10 Dec 2006 20:58:19 +0100
From:	Pavel Machek <pavel@....cz>
To:	Wouter Verhelst <wouter@...p.be>
Cc:	Paul Clements <paul.clements@...eleye.com>, akpm@...l.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nbd: show nbd client pid in sysfs

Hi!

> > > This simple patch allows nbd to expose the nbd-client 
> > > daemon's PID in /sys/block/nbd<x>/pid. This is helpful 
> > > for tracking connection status of a device and for 
> > > determining which nbd devices are currently in use.
> > 
> > Actually is it needed at all? Perhaps nbd clients should be modified
> > to put nbdX in their process nam?
> 
> I don't think that's the right approach; only the kernel can guarantee
> that a given process is actually managing a given nbd device (I could
> have some rogue process running around announcing that it's managing
> nbd2, and then what?)

I'd say "do not run rogue processes as root" :-).

nbd-client should run as root -- I do not think interface was
carefully audited to run it as a user -- so rogue process should not
really be a problem.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/