> +#undef unlink
> +int cygwin_unlink(const char *pathname)
> +{
> + /* "read-only" files can't be unlinked */
> + chmod(pathname, 0666);
> + return unlink(pathname);
> +}
I've no idea on how cygwin maps file permissions to the underlying
filesystem, but the above raised my attention. Doesn't chmodding the file
to 0666 open a small windows where "group" and "other" users have read
access to the file? This might be unwanted by the user and could be
exploited by some attacker listening for changes on that file.
Or am I too paranoid?
Regards,
Chris
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html