diff options
| author | cel <cel@FreeBSD.org> | 2006-04-02 04:24:57 +0000 |
|---|---|---|
| committer | cel <cel@FreeBSD.org> | 2006-04-02 04:24:57 +0000 |
| commit | 08249d49bf1e9291264b2b58268dcc682525df9e (patch) | |
| tree | 971cf41abd148bcc5fc997282029923ee4757e5c /usr.sbin/praliases | |
| parent | 85222c8750f2e70f6975f8a43e7e4d2c9722bebc (diff) | |
| download | FreeBSD-src-08249d49bf1e9291264b2b58268dcc682525df9e.zip FreeBSD-src-08249d49bf1e9291264b2b58268dcc682525df9e.tar.gz | |
rick says:
The following bug was just identified in OpenBSD and it looks like the same
bug exists in the other BSDen NFS servers.
A Linux client (don't know which version, but you can look at
http://bugzilla.kernel.org/show_bug.cgi?id=6256)
does a Setattr of mtime to the server's time, where the file is mode 0664 and
the client user has group access (ie. caller is not the file owner).
The BSD servers fail the Setattr with EPERM, since the VA_UTIMES_NULL flag
isn't set before doing the VOP_SETATTR.
It seems to me that this should be allowed, since it is allowed for a local
utimes(2). If so, the fix is to set VA_UTIMES_NULL for the
"set-time-to-server-time" cases of setting atime and/or mtime.
Submitted by: rick@snowhite.cis.uoguelph.ca
Reviewed by: cel
Approved by: silby
MFC after: 1 week
Diffstat (limited to 'usr.sbin/praliases')
0 files changed, 0 insertions, 0 deletions
