🚀 go-pugleaf

molenda@i9.msi.umn.edu (Jason Molenda) writes:

>davidg@aegis.or.jp (Dave McLane) writes:

>>Any other ideas anybody?

>hack the reader?  i.e. see if you can't rip the 'g' guts out of rn (so
>they can only read one group at a time) and add code to do
>authorization based on an access file (aka ACLs) at startup so they need
>to type "rn <grpname>".

I haven't looked at the code, but I would have thought you could
just add a call to make that check at the point rn/nn/etc. are
changing groups. 

A brief look at rn shows these fragments in ng.c:

=== fragment 1 from ng.c ===
    if (eaccess(ngdir,5)) {		/* directory read protected? */
	if (eaccess(ngdir,0)) {
#ifdef VERBOSE
  	    IF(verbose)
		printf("\nNewsgroup %s does not have a spool directory!\n",
		    ngname) FLUSH;
	    ELSE
#endif
#ifdef TERSE
		printf("\nNo spool for %s!\n",ngname) FLUSH;
#endif
============================

=== fragment 2 from ng.c ===
============================
    /* chdir to newsgroup subdirectory */

    if (chdir(ngdir)) {
	printf(nocd,ngdir) FLUSH;
	mode = oldmode;
	return -1;
    }
============================

>I have no idea how modular the goto-next-group code is in rn.  I'm just
>throwing an idea out.  I think you're going to end up with a gross
>hack no matter what you do.

The rn/nn I'n running have already been hacked to allow them to
work with Japanese so what's one more hack :-)

Dave

--
Dave McLane 
JUNET: davidg@aegis.or.jp (ONLY within Japan: post otherwise)
Nagaokakyoshi, Kyoto Japan Tel: +81-75-951-1168 Fax: +81-75-957-1087