linux-kernel - Re: utimes() with vfat is problematic

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]

Message-ID: <ec870ced0707100318g87f22f8wcaa6a715c064338@mail.gmail.com>
Date:	Tue, 10 Jul 2007 12:18:17 +0200
From:	"Pawel Dziepak" <hryssta@...il.com>
To:	"Jan Engelhardt" <jengelh@...putergmbh.de>
Cc:	linux-fsdevel@...r.kernel.org,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	hirofumi@...l.parknet.co.jp
Subject: Re: utimes() with vfat is problematic

2007/7/10, Jan Engelhardt <jengelh@...putergmbh.de>:
> I am not sure how this could be dealt with besides passing -o quiet to
> mount.vfat. Any ideas?

The problem is in the function utimes. I have mounted vfat partition
as a root, then changed permissions to 777 for all files. However, I
wasn't be able to touch any file (changing date to the  past) as a
normal user. utimes() should check write permission instead of uid/
I didn't read 'touch' source code and it is probably caused by it's
procedures that I was able to change modification date to the current
date.
Single UNIX Specification says crealy that to do utimes on a file user
have to had write permissions or be a file owner.

Pawel
-
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/