Nis Martensen wrote:
Without this, the CGI was creating web pages that had no
other-read permissions, (which meant that apache couldn't
serve them unless they happened to belong to the same group
as the apache process (www-data I believe?)).
This has been requested a few times before, my
On Tue, 13 Nov 2007 15:32:33 -0500, Joey Hess wrote:
I suppose it could be implemented as an option. Although wouldn't it be
better for apache itself to have an option for setting the umask? I'm
sure there are other cgi scripts that write files with unexpected modes
when apache inherits an
Third part of this patch submission series. The patch below (by cworth)
is currently in use in cairographics.org's version of ikiwiki. Since the
subject matches, I am sending this to an existing bug report.
Subject: [PATCH] Explicitly set umask to 0002 in wrapper
Without this, the CGI was
tags 443329 wontfix
thanks
also sprach Joey Hess [EMAIL PROTECTED] [2007.09.21.0139 +0100]:
Well, people use ikiwiki in lots of ways that don't always necessarily
involve public web sites, or web sites at all.
Alright then, I'll tag it wontfix for now. Would it make sense to
have the umask to
martin f krafft wrote:
Alright then, I'll tag it wontfix for now. Would it make sense to
have the umask to use be a configuration item?
Maybe.. I was thinking it might makes sense for ikiwiki to preserve
input file/directory permissions.
--
see shy jo
signature.asc
Description: Digital
also sprach Joey Hess [EMAIL PROTECTED] [2007.09.21.1745 +0100]:
Alright then, I'll tag it wontfix for now. Would it make sense to
have the umask to use be a configuration item?
Maybe.. I was thinking it might makes sense for ikiwiki to preserve
input file/directory permissions.
Well,
Package: ikiwiki
Version: 2.6.1
Severity: wishlist
When ikiwiki writes the HTML files to the output directory, it does
so according to the umask. I think that does not make sense as the
output files should always be at least 644. It would be nice if
ikiwiki overrode umask with 002.
-- System
martin f krafft wrote:
When ikiwiki writes the HTML files to the output directory, it does
so according to the umask. I think that does not make sense as the
output files should always be at least 644. It would be nice if
ikiwiki overrode umask with 002.
Why should the output files always be
also sprach Joey Hess [EMAIL PROTECTED] [2007.09.20.1914 +0100]:
Why should the output files always be at least 0644? They could contain
data of any kind, so allowing a umask to prevent them from being seen
seems like a good idea to me.
I've always found making programs ignore the umask to
martin f krafft wrote:
I see your argument, but isn't this wiki data, and wiki data by
default intended for the public, i.e. o+rX?
Well, people use ikiwiki in lots of ways that don't always necessarily
involve public web sites, or web sites at all.
--
see shy jo
signature.asc
Description:
10 matches
Mail list logo
