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: hide headers (Julien ?LIE)
2. Re: hide headers (Nick Edwards)
3. Re: hide headers (Nick Edwards)
4. access question (Nick Edwards)
----------------------------------------------------------------------
Message: 1
Date: Mon, 08 Sep 2014 21:59:59 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: hide headers
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Nick,
> we need to sort out some hiding of headers.
[...]
> I get "addnntppostinghost: false" but how do we stop all of the other
> X-trace and X-X stuff that identifies a poster?
Besides Steve's wise answer I also recommend regarding the X-Trace:
header field, I suggest you have a look at:
<http://www.eyrie.org/~eagle/faqs/inn.html#S6.11>
---
Hide the Injection-Info header
There is no built-in support for suppressing generation of the
Injection-Info header. You can, however, remove it from inside a Perl
posting filter. Try using a posting filter like this:
sub filter_post {
$modify_headers = 1;
delete $hdr{'Injection-Info'};
return '';
}
Note that you have to set $modify_headers to make changes to the article
header effective in the actual posted article. Instead of removing the
header, you can also alter it if you modify $hdr{'Injection-Info'}.
---
This method of course works for other headers.
I hope it answers your needs in case you wish to hide other headers than
the X-Trace: one or the Injection-Info: one.
More information about posting filters:
<http://www.eyrie.org/~eagle/software/inn/docs/hook-perl.html#S5>
And welcome to INN by the way. Do not hesitate to ask questions here or
in news.software.nntp in case you need some help.
--
Julien ?LIE
? Obsequium amicos ueritas odium parit. ? (T?rence)
------------------------------
Message: 2
Date: Tue, 9 Sep 2014 10:16:30 +1000
From: Nick Edwards <[email protected]>
To: [email protected]
Subject: Re: hide headers
Message-ID:
<CAMD-=VLRZCnQjc_mi0NAe5pPVY2K6jm_yUDa4nmNQ3a=b-w...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 9/8/14, Steve Crook <[email protected]> wrote:
> On Mon, Sep 08, 2014 at 02:25:49PM +1000, Nick Edwards wrote:
>> Hello,
>> First of all, inn newbie alert, not a newsmaster newbie having used
>> dnews for 15 years, but dnews is not ipv6 capable, nor have/will they
>> release a 64bit binary and they have no intention on releasing source
>> code to build same, otherwise its served us real well, but, the time
>> has come to change for ipv6 use which has become mandatory due to ipv4
>> exhaustion, good thing is dnews refeed option allowing us to push all
>> existing articles to our new inn box, all works well with inn, in our
>> dev setup, but before we change DNS and have inn the real news server
>> in production, we need to sort out some hiding of headers.
>>
>> I get "addnntppostinghost: false" but how do we stop all of the
>> other X-trace and X-X stuff that identifies a poster? (We use IP
>> range access not some remote database if that matters)
>
> Hi Nick,
>
> Hopefully this answers your question:
> http://www.mixmin.net/cleanfeed/faq.html#hashhost
>
> There are two examples given. Depending on your combination of Perl
> and INN versions, you might need to tweak one of them to suit your
> environment.
Thanks, have added that, and about to restart to test :-)
------------------------------
Message: 3
Date: Tue, 9 Sep 2014 10:19:01 +1000
From: Nick Edwards <[email protected]>
To: Julien ?LIE <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: hide headers
Message-ID:
<CAMD-=VLiq+eF0x3a=diJM_6D9cuStVauev4_=t+qal1nbxy...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 9/9/14, Julien ?LIE <[email protected]> wrote:
> Hi Nick,
>
>> we need to sort out some hiding of headers.
> [...]
>> I get "addnntppostinghost: false" but how do we stop all of the other
>> X-trace and X-X stuff that identifies a poster?
>
> Besides Steve's wise answer I also recommend regarding the X-Trace:
> header field, I suggest you have a look at:
> <http://www.eyrie.org/~eagle/faqs/inn.html#S6.11>
>
> ---
> Hide the Injection-Info header
>
> There is no built-in support for suppressing generation of the
> Injection-Info header. You can, however, remove it from inside a Perl
> posting filter. Try using a posting filter like this:
>
> sub filter_post {
> $modify_headers = 1;
> delete $hdr{'Injection-Info'};
> return '';
> }
>
> Note that you have to set $modify_headers to make changes to the article
> header effective in the actual posted article. Instead of removing the
> header, you can also alter it if you modify $hdr{'Injection-Info'}.
> ---
>
> This method of course works for other headers.
> I hope it answers your needs in case you wish to hide other headers than
> the X-Trace: one or the Injection-Info: one.
>
>
>
> More information about posting filters:
> <http://www.eyrie.org/~eagle/software/inn/docs/hook-perl.html#S5>
>
>
> And welcome to INN by the way. Do not hesitate to ask questions here or
> in news.software.nntp in case you need some help.
>
>
Thanks, with this and Steve's, I think I got it nutted out, have one
more question, but to keep uniformity I'll start a new thread.
------------------------------
Message: 4
Date: Tue, 9 Sep 2014 10:25:14 +1000
From: Nick Edwards <[email protected]>
To: "[email protected]" <[email protected]>
Subject: access question
Message-ID:
<CAMD-=vlsodqr+uykgvoshwq14eyfzusfe3k+o75ifqpquzq...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
I think I have the access file sorted but to make sure, our readers.conf is
auth "localhost" {
hosts: "localhost, 127.0.0.1, ::1, stdin"
default: "<localhost>"
}
access "localhost" {
users: "<localhost>"
newsgroups: "*"
access: RPA
}
auth custs {
hosts: "IP.RA.NG.E/CIDR, *.anotherdomain, *.yetanotherdomain"
default: <custs>
}
access custs {
newsgroups: *
}
If my reading on man is right, this appear secure, but is it
appropriate? Do we need a users: line or is it implied ?
Thanks
Nik
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 64, Issue 4
******************************************
