Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: nnrp conf (Julien ?LIE)
2. Re: nnrp conf (Noel Butler)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 Dec 2014 22:08:04 +0100
From: Julien ?LIE <[email protected]>
To: [email protected], Edwardo Garcia <[email protected]>
Subject: Re: nnrp conf
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Edwardo,
>> auth example.com {
>> hosts: "*.example.com, example.com"
>> default: <LOCAL>
>> }
>>
>> access full {
>> newsgroups: *
>> }
>
> this brackets comment with LOCAL says localhost , so much confusion,
I suggest the following wording for the documentation.
Would it be clear enough or should something else be explained?
?
Probably the simplest useful example of a complete readers.conf,
this gives permissions to read and post to all groups to any connections
from the "example.com" domain, and no privileges for anyone connecting
elsewhere:
auth example.com {
hosts: "*.example.com, example.com"
default: "<EXAMPLE>"
}
access full {
newsgroups: *
}
Note that the access realm has no users: key and therefore applies
to any user identity (in this example, the user identity that will be
assigned to all matching connections is <EXAMPLE>). The only
available auth realm only matches hosts in the "example.com" domain,
though, so any connections from other hosts will be rejected immediately.
?
--
Julien ?LIE
? Science sans conscience n'est que ruine de l'?me. ? (Rabelais)
------------------------------
Message: 2
Date: Wed, 17 Dec 2014 08:39:09 +1000
From: Noel Butler <[email protected]>
To: Julien ?LIE <[email protected]>
Cc: [email protected]
Subject: Re: nnrp conf
Message-ID: <1418769549.3893.11.camel@tardis>
Content-Type: text/plain; charset="utf-8"
On Tue, 2014-12-16 at 22:08 +0100, Julien ?LIE wrote:
>
> I suggest the following wording for the documentation.
> Would it be clear enough or should something else be explained?
>
>
> ?
> Probably the simplest useful example of a complete readers.conf,
> this gives permissions to read and post to all groups to any connections
> from the "example.com" domain, and no privileges for anyone connecting
> elsewhere:
>
> auth example.com {
> hosts: "*.example.com, example.com"
> default: "<EXAMPLE>"
> }
>
> access full {
> newsgroups: *
> }
>
> Note that the access realm has no users: key and therefore applies
> to any user identity (in this example, the user identity that will be
I would suggest adding the users: <EXAMPLE> key in the access section,
I can see how some may, and I also did at first read, read this as allow
anyone to read/write any group, perhaps its where OP went wrong
somewhere and found himself with an open system, so making it crystal
clear for those not "familiar" with inn would be better.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20141217/b015cddf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20141217/b015cddf/attachment-0001.bin>
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 67, Issue 10
*******************************************
