On lun, 2009-05-04 at 17:35 +1000, Tim Connors wrote: > Yes, I'm saying they should be created with more restrictive defaults. > > > evolution should just use what the > > current umask is. If you want it to another value, just set it in you > > environment before running evolution (isn't that the purpose of umask > > anyway?). Multi-user systems running evolution aren't that frequent, I > > guess (multi-user systems aren't that frequent anyway, these days) and > > you can adjust the permissions for your ~ and .evolution in a lot of > > different ways. No need to add complexity to that huge stack of code. > > Family machines? (eg, the machine I found this bug on. I myself wouldn't > use evolution or indeed desktop environments if I was forced at gunpoint, > but that's what mum uses.
I didn't say there were no multi-user machines. I was just saying that
they weren't the most common environment.
> In desktop environments, good luck setting a
> sensible umask.)
Just set it in .xsessionrc.
>
> What kind of complexity is
>
> int main(...) {
> umask(0700);
> ...
> }
And then you can't chose anything else if you want to, which makes me a
little uncomfortable.
Cheers,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
