🚀 go-pugleaf

Kent C. Brodie writes:
>1) If I run tin as setuid-tin, then is having tind doing anything for me?

As far as I understand it (but I'm not official in this) you have three
ways to set things up:
  
  [Tin not setuid, no tind] For people who have no privs on their system, 
  this is the way to go. Indexing is then done in the $HOME directory of
  the user that uses tin. There is an option to make tin do indexing in
  the back ground while reading news. If you don't use that option it'll
  index each group just before you read the news in it (taking time for it).
  
  [tin not setuid, tind] For system administrators who feel anxious to give
  away news privileges (chmod +s news), but still are keen on disk usage, 
  this tind (of course setuid) does the indexing during off-hours, while
  ordinary users just use tin for _reading_ the news, which doesn't need
  provileges since the news spoold dir is world readable.
  
  [tin setuid, no tind] Since tin itself is sufficiently privileged to
  write in the news spool directory, it can update the central index files
  itself. Running 'tin -u' from cron at some well chosen times will do the
  same as the tin daemon. Setuid programs can always be a breach of system
  security, so this option must be chosen with appropriate care. On the
  other hand: this is the most simple setup: just one program doing all.
  
I must point out that this is just my personal impression that I have
of how tin/tind works. I do hope that Iain can enlighten us, since both
Ken and I still have problems.
  
>2) If I run tin as setuid, then the indexing seems to work OK, but
>   then users editing comes up in read-only.

I run tin setuid. I don't seem to have the read-only editing session,
but I do have the setuid(real) failure message.

>3) if I don't* run setuid tin, then I get users seeing
>   "Permission denied" errors on the central index files.

This is not explanable with the above three points: not-setuid tin 
apparently assumes that if central index files exist, updating
should be done centrally too. I had expected that not-setuid tin
would just put its index in $HOME, no matter which other index
files already exist. 

>Iain---   PLEASE help us,...   can you explain in detail
>how this is REALLY supposed to work, properly, assuming we use tind??

Yes, Iain, would you please?

Met vriendelijke groeten, Wim `Blue Baron' van Dorst
-- 
---------------------------------------------------------------------
Blue Baron = Wim van Dorst, Voice (+31) 074-443937, (+31) 02152-42319
(-: baron@clifton.hobby.nl  tgcpwd@urc.tue.nl  WvD@Akzo.400net.nl :-)
---------------------------------------------------------------------