[rsbac] a few problems

[Amon Ott]

On Friday, 13. September 2002 18:09, Josh Beagley wrote:
> > On Monday, 9. September 2002 09:25, Josh Beagley wrote:
> > > The first problem I seem to be having is enabling FF flags
> > add_inherited > and secure_delete on my home directory. I am
> > running rsbac 1.2.0, kernel > 2.4.19 and the preemptive patch. I
> > get the following error, and and process > involving file
> > operations hangs: > 
> > > Sep  7 02:13:02 Lynx kernel: Assertion failure in
> > ext3_sync_file() at > fsync.c:55: "ext3_journal_current_handle()
> > == 0" > Sep  7 02:13:02 Lynx kernel: kernel BUG at fsync.c:55!
> > 
> > This is caused by the RSBAC secure delete code calling fsync,
> > although the  journal is currently open.
> > 
> > The attached patch avoids fsync for ext3. However, although it
> > seems that the  zeroed file is synced to disk by the ext3 code, I
> > cannot guarantee the  overwriting on disk.
> > 
> > This would need some direct testing, e.g. secure deleting on a
> > loop mount or  floppy disk and grepping for the file contents
> > afterwards. Volunteers? 

> well, after recompiling rsbac with the attached patch, I created a file
> with the contents being the word "nongoword", which I then deleted, and of
> course i enabled secure delete for the directory the file was in. Using the
> lde tool, which examines and recoveres deleted files from a ext2 partition,
> i was able to search for the phrase "nongoword" and recover the file.

OK, I will try to code my own fsync in ext3 to avoid the problem.

Amon.
--
http://www.rsbac.org