Support Cancel-Lock about inn HOT 5 CLOSED

RFC 8315 has now standardized Cancel-Lock, and a new libcanlock3 library has been released. We have to implement:

• the generation of Cancel-Lock and Cancel-Key header fields in nnrpd, along with a new inn-secrets.conf file to store the secrets;
• the verification of these header fields in innd;
• a generator of cancels (notably for the news administrator, so that he can easily retrieve the key and post cancels in case of abuse).

from inn.

Comment by iulius on 21 Dec 2008 21:28 UTC
The draft can be found at http://tools.ietf.org/html/draft-ietf-usefor-cancel-lock-01.

from inn.

Comment by iulius on 21 Dec 2008 21:30 UTC
Another approach by Alexander Bartolich:

https://code.th-h.de/?p=usenet/INN.git

Also see (in German):

news:[email protected]
news:[email protected]

from inn.

@Julien-Elie Is it possible to implement IP-based hashes generation to use them when access groups are shared between several people? This allows to cancel messages for users who are not authorized on the server.

from inn.

I've implemented addcanlockuser (boolean) in readers.conf access groups that can be set to true (the default, add a user Cancel-Lock hash based on the authenticated username) or false (no user Cancel-Lock hash).
I understand your proposal. Would changing addcanlockuser to a string with the following behaviour suit your needs?

• username: the default, add a user Cancel-Lock hash based on the authenticated username
• ip: add a user Cancel-Lock hash based on the IP of the connected client
• none: no user Cancel-Lock hash

from inn.