On Wed, Apr 4, 2012 at 2:05 AM, Bryn M. Reeves wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/03/2012 04:56 PM, Joel Rees wrote:
>> Good point. I don't visit those sites, and it's important for me
>> to mention that. No p0rn, period, and many of the moral reasons are
>> in
>
>
On Tue, Apr 3, 2012 at 9:31 PM, Tim wrote:
> On Tue, 2012-04-03 at 16:10 +0900, Joel Rees wrote:
>> Well, there is a reason some people don't want universal ID, for example.
>> It's a lot broader topic than you may want to believe. It's similar to the
>> reason your httpd and ftpd (ntpd, nfs daemo
On Tue, 2012-04-03 at 16:10 +0900, Joel Rees wrote:
> Well, there is a reason some people don't want universal ID, for example.
> It's a lot broader topic than you may want to believe. It's similar to the
> reason your httpd and ftpd (ntpd, nfs daemon, database daemons, etc.)
> are operating as sep
(woops, missed the user list)
On Tue, Apr 3, 2012 at 5:47 PM, Bryn M. Reeves wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/03/2012 08:10 AM, Joel Rees wrote:
>> On Tue, Apr 3, 2012 at 3:27 PM, Tim
>> wrote: s/some/a lot of/
>>
>> if you set it up right.
>
> It can still do a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/03/2012 08:10 AM, Joel Rees wrote:
> On Tue, Apr 3, 2012 at 3:27 PM, Tim
> wrote: s/some/a lot of/
>
> if you set it up right.
It can still do a fair amount of nasty stuff.
> "xhost local:; sudo -u " does pretty well
> with current applicatio
On Tue, Apr 3, 2012 at 3:27 PM, Tim wrote:
> Tim:
>>> It always struck me that personal files ought to have no group or
>>> world permissions set by default. If you wanted your files to have
>>> those extra permission set, then it ought to be done as a deliberate
>>> choice.
>>
> Joel Rees:
>> Ma
Tim:
>> It always struck me that personal files ought to have no group or
>> world permissions set by default. If you wanted your files to have
>> those extra permission set, then it ought to be done as a deliberate
>> choice.
>
Joel Rees:
> Maybe "user-id" is mis-named. There are sure a lot of p
On Sat, Mar 31, 2012 at 7:04 PM, Tim wrote:
> On Fri, 2012-03-30 at 20:39 +0100, James Wilkinson wrote:
>> From there, it follows that the easiest way to do this is to make 002
>> the default umask, which means that all new files and directories
>> created by normal users have these permissions. T
