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] [day] [month] [year] [list]

Date:	Tue, 10 Jul 2007 18:54:35 +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

On 7/10/07, Jan Engelhardt <jengelh@...putergmbh.de> wrote:
> Linux does check for write permission, but _only_ for time=NULL.
> Hence it would be helpful if someone knows the exact SUS text,
> or whether this is not explicitly specified in SUS, leaving room
> for interpretation.
I have already checked it strictly. This "problem" occurs not only on
vfat partitions. You can *not* do uptime() for time!=NULL if you are
not a file owner. So, everything in Linux is correct.
It is not possible to solve your problem without changing SUS, it is
not even a problem...
I made mistake in my first post, because I was too implied by piece of
code that you've quoted.

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/