• Re: RFC 8315 perl hooks for Inn (was: Re: Systems running news servers)

    From Thomas Hochstein@thh@thh.name to news.software.nntp on Sun Aug 23 15:12:05 2026
    From Newsgroup: news.software.nntp

    Julien +LIE wrote on 2021-02-08,
    quoting Gorald Niel:

    https://code.th-h.de/?p=usenet/INN.git;a=tree;f=filter

    I think I've succeffuly rewrited those hooks to be RFC 8315 compliant.

    If that works and looks good, tell me how to (and where) submit these.

    As Thomas reads this newsgroup, just provide a link to your patch.
    Thanks for it!

    Thanks again to Gorald!

    I've now (some years later ...) updated my code.
    (Currently here: <https://code.virtcomm.de/thh/INN-config/>)

    For INN 2.7.0 and newer, those changes to filter_innd.pl or
    cleanfeed.local are now obsolote as INN has native support for Cancel-Lock/-Key, if compiled accordingly. For older versions, the
    code may still be of value.

    You may still need the code in filter_nnrpd.pl if you change the
    Message-ID in this filter. Yes, you should never change a Message-ID,
    even in a posting filter, but you may want to under special
    cirumstances. I do that in my local installation, triggered only for
    my own client, to generate more "meaningful" Message-IDs. If you
    change Message-IDs in filter_nnrpd.pl, you have to replace submitted Cancel-Lock/-Key headers, too, because they are generated by INN (or a newsreader) before filter_nnrpd.pl is run.

    Due to those special circumstances, my filter_nnrpd.pl implementation
    can now either add news hashes to existing Cancel-Lock/-Key headers or completely replace the current headers. You can also choose how many
    and what hashes to use (sha1, sha256 and/or sha521). For INN 2.7.0 and
    onwards, the code will get the secrets from inn-secrets.conf; for
    older versions, you have to supply the secret in code, as usual.

    So, both filter_nnrpd.pl and cleanfeed.local will work for older
    versions of INN (or if you don't want to use the native support [1]),
    and filter_nnrpd.pl will work with INN 2.7 to replace Cancel-Lock/-Key
    headers if you're already messing with Message-IDs in filter_nnrpd.pl.

    [1] You will need an inn-secrets.conf file for INN 2.7.0 and newer.

    -thh
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Julien_=C3=89LIE?=@iulius@nom-de-mon-site.com.invalid to news.software.nntp on Tue Sep 1 14:12:16 2026
    From Newsgroup: news.software.nntp

    Hi Thomas,

    Thanks again to G|-rald!

    Yes! I've forwarded your message to him. I am really unsure he still
    reads Usenet newsgroups.


    I've now (some years later ...) updated my code.
    (Currently here: <https://code.virtcomm.de/thh/INN-config/>)

    Due to those special circumstances, my filter_nnrpd.pl implementation
    can now either add news hashes to existing Cancel-Lock/-Key headers or completely replace the current headers. You can also choose how many
    and what hashes to use (sha1, sha256 and/or sha512). For INN 2.7.0 and onwards, the code will get the secrets from inn-secrets.conf; for
    older versions, you have to supply the secret in code, as usual.

    A nice move. Thanks for the improvement and refresh of the scripts!
    --
    Julien |eLIE

    -2-arCo Mais je leur ai simplement demand|- si c'|-tait la bonne route-a!!!
    rCo Ils nous ont fait une '|-ponse de No'mand-a!-a-+ (Ast|-rix)

    --- Synchronet 3.22a-Linux NewsLink 1.2