[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#342455: tech-ctte: Ownership and permissions of device mapper block devices



On Tue, Jan 03, 2006 at 03:26:30PM +0000, Ian Jackson wrote:
> Thanks for your patches.  I don't have time right know to look at the
> technicalities in detail.

I did not get any response about the patches from upstream yet. 

>                            Do we have all of the relevant Debian LVM
> and devmapper reading this thread ?  If not we should make sure that
> they look at it.

There are 5 reverse dependencies to devmapper: lvm2, lilo,
multipath-tools, dmraid, cryptsetup.

I can speak for lvm2 and multipath-tools. lilo is not affected by this
problem, as it only uses them to find block numbers. The remaining
packages are dmraid and cryptsetup.

I don't think they got knowledge about that thread. Can you post a
pointer?

> I'm also encouraged by the fact that you've written patches at all;
> this suggests that you do seem to be taking the matter seriously,

I developed the idea for this fix some months ago, but never found the
time to implement it. So I should have refrained from tagging the bugs
wontfix.

The lvm2 patch lacks one additional functionality where I don't know if
it is possible to implement: I want to make the permissions dependent on
the metadata tags or just record them in the metadata.

> although your comments don't always give that impression.

This may be a sign for beeing overloaded. I just try to finish my
prediploma and the mathematics course needs a lot of work.

> If you're finding it difficult to write long and coherent explanations
> in English please feel free to write in German.  My German is probably
> good enough to understand your points if you spell them out clearly
> (and at length!) and I would be happy to try to act as an
> intermediary.

Thank you for the offer.

Bastian

-- 
No one may kill a man.  Not for any purpose.  It cannot be condoned.
		-- Kirk, "Spock's Brain", stardate 5431.6

Attachment: signature.asc
Description: Digital signature


Reply to: