linux-ext4 - Re: [e2fsprogs] initdir: Writing inode after the initial write?

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, 4 Dec 2012 14:08:29 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Darren Hart <dvhart@...radead.org>
Cc:	Andreas Dilger <aedilger@...il.com>,
	Andreas Dilger <adilger@...ger.ca>,
	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: [e2fsprogs] initdir: Writing inode after the initial write?

On Tue, Dec 04, 2012 at 09:43:21AM -0800, Darren Hart wrote:
> > "modify_inode" is not a terribly easy use interface. Probably better to add something like "chmod" and "chown" for debugfs as well. 
> 
> I was thinking the same thing.
> 

modify_inode is the old command, and it is indeed hard to use.  The
new one (and the one I use all the time) is set_inode_field
(abbreviation "sif"):

    sif /bin/su mode 0104755
    sif /bin/su uid 0

BTW, one of the things that I've always toyed with was to create a
shim layer between the libss API and the tcl embedding API, which
would add some scripting, aliases, and automation relatively easily to
debugfs.

What people have done in practice who have cared about this is to
create perl scripts which emits a series of commands which they then
feed to a pipe which has debugfs on the other end.

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html