filepermissons

filepermissons

[Markus Linnala]

Is there a way to make all .newsrc* stuff permanently unreadable to
group & others? I know what umask is. I don't want to change it.

*dribble and *~ files get their permissions from umask, not from
.newsrc as I'd like them to get.

How about variable gnus-keep-newsrc-permissions. It should keep
.newsrc* permissions according to .newsrc.

--
//Markus

Re: filepermissons

[Karl_Kleinpaste]

Markus Linnala <maage@cs.tut.fi> writes:
>Is there a way to make all .newsrc* stuff permanently unreadable to
>group & others?

There is no good excuse for having .newsrc* in ~ in the 1st place.

mkdir ~/.private
chmod 700 ~/.private	# or, under AFS, "fs sa ~/.private -clear you rlidkwa"
mv ~/.newsrc* ~/.private
(setq gnus-startup-file "~/.private/.newsrc"
      mail-archive-file-name "~/.private/.outgoing"
      gnus-author-copy "~/.private/.news")

Embellish to taste.

Re: filepermissons

[Lars Magne Ingebrigtsen]

Markus Linnala <maage@cs.tut.fi> writes:

> Is there a way to make all .newsrc* stuff permanently unreadable to
> group & others? I know what umask is. I don't want to change it.
> 
> *dribble and *~ files get their permissions from umask, not from
> .newsrc as I'd like them to get.

Hmn.  The *dribble autosave files do not normally have a corresponding
"real" file.  How does one specify the file permissions for that file
then? 

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."

Re: filepermissons

[Colin Rafferty]

Lars Magne Ingebrigtsen writes:
> Markus Linnala <maage@cs.tut.fi> writes:

>> Is there a way to make all .newsrc* stuff permanently unreadable to
>> group & others? I know what umask is. I don't want to change it.

> Hmn.  The *dribble autosave files do not normally have a corresponding
> "real" file.

Sure they do.  In fact, I have the following in my .gnus to make certain
of that:

    (add-hook 'gnus-summary-exit-hook 'gnus-dribble-save)

> How does one specify the file permissions for that file
> then?

In `gnus-dribble-read-file' after the call to `set-visited-file-name':

    (set-file-modes dribble-file (+ (* 6 64) (* 0 8) (* 0 1)))

; Colin

Re: filepermissons

[Lars Magne Ingebrigtsen]

craffert@sps.ml.com (Colin Rafferty) writes:

> > Hmn.  The *dribble autosave files do not normally have a corresponding
> > "real" file.
> 
> Sure they do. 

No, they do not normally have corresponding "real" files.

> In `gnus-dribble-read-file' after the call to `set-visited-file-name':
> 
>     (set-file-modes dribble-file (+ (* 6 64) (* 0 8) (* 0 1)))

(set-file-modes "~/.newsrc-soup-dribble" 644)
=> Signalling: (file-error "Doing chmod" "no such file or directory"
                 "/home/lars/.newsrc-soup-dribble")

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."

Re: filepermissons

[Colin Rafferty]

Lars Magne Ingebrigtsen writes:
> craffert@sps.ml.com (Colin Rafferty) writes:

>>> Hmn.  The *dribble autosave files do not normally have a corresponding
>>> "real" file.

>> Sure they do.

> No, they do not normally have corresponding "real" files.

Okay, you are correct.

>> In `gnus-dribble-read-file' after the call to `set-visited-file-name':

>> (set-file-modes dribble-file (+ (* 6 64) (* 0 8) (* 0 1)))

> (set-file-modes "~/.newsrc-soup-dribble" 644)
> => Signalling: (file-error "Doing chmod" "no such file or directory"
>                  "/home/lars/.newsrc-soup-dribble")

Very good point.  However, you can put it immediately after the call to
`save-buffer' in `gnus-dribble-save'.

--
Colin

Re: filepermissons

[Lars Magne Ingebrigtsen]

craffert@sps.ml.com (Colin Rafferty) writes:

> > (set-file-modes "~/.newsrc-soup-dribble" 644)
> > => Signalling: (file-error "Doing chmod" "no such file or directory"
> >                  "/home/lars/.newsrc-soup-dribble")
> 
> Very good point.  However, you can put it immediately after the call to
> `save-buffer' in `gnus-dribble-save'.

That's true.  Some people are very secretive, though.  There should be
a way to specify the file permissions of the auto-saved dribble file.
One does not want people to know that one is reading
"comp.language.c++".  :-)

Hm.  Perhaps there is no way to do this in a straightforward manner?
Perhaps I could just write the dribble buffer to a file when I open
the buffer and set the file permissions then?  Yes, that should
work.. 

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."

Re: filepermissons

[Hallvard B Furuseth]

> Some people are very secretive, though.  There should be
> a way to specify the file permissions of the auto-saved dribble file.
> One does not want people to know that one is reading
> "comp.language.c++".  :-)

Right.  So why not just let the default mode for files and directories
that gnus by default creates in $HOME, be 0600.  If you can infer a
better mode from ~/.newsrc or whatever, fine.  But while people can and
do complain about lack of privacy, I don't really expect anyone to
complain because their dribble file isn't public.


Regards,

Hallvard