Path: ...!news.mixmin.net!aioe.org!news.alphanet.ch!alphanet.ch!.POSTED.catalyst.alphanet.ch!not-for-mail From: Marc SCHAEFER Newsgroups: fr.usenet.abus.d Subject: Re: =?ISO-8859-1?Q?vir=E9?= de eternal-september.org ? Date: Mon, 16 May 2022 11:22:52 -0000 (UTC) Organization: Posted through ALPHANET Message-ID: References: <6hs28htd6fvp9jfhanogilavghc0q805a1@consensus-omnium> <9cs38h9g7vo0j8df60k05pvpv9se7en6tl@consensus-omnium> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 16 May 2022 11:22:52 -0000 (UTC) Injection-Info: shakotay.alphanet.ch; posting-account="schaefer"; posting-host="catalyst.alphanet.ch:192.168.99.121"; logging-data="11607"; mail-complaints-to="usenet@alphanet.ch" User-Agent: tin/2.4.3-20181224 ("Glen Mhor") (UNIX) (Linux/4.19.0-20-amd64 (x86_64)) Cancel-Lock: sha256:6v/XdYDv7eARFRpRITToAn63/7TSw90ZWzEaQWWOIY8= Bytes: 3186 Lines: 46 Marc SCHAEFER wrote: > Reste que mes logs montrent: May 14 11:17:30 shakotay innd: filter: No Cancel-Key[sha1:PcZKXYJ4SBnNoOw7/KSwrvQdwPc=] matches Cancel-Lock[sha1:evftDpVUw+bvdzR4HbC54X4U0uw= sha256:zIRVEWsR0lLgCFQEntUND26UI5z81OSdGUAMFCcJW/Q=] target= > > et on voit clairement que le 3e -- le seul qui marche -- a été zappé. Hmm. Voici un test qui montre le problème: $ ./test-cancel-multiline.sh inews: cannot send article to server: 441 437 No Cancel-Key matches Cancel-Lock. target= inews: article not posted avec art1 l'article: From: Marc SCHAEFER Subject: Supersedes: and Cancel-Key Message-ID: Newsgroups: alphanet.test Cancel-Lock: sha256:Gfz9ElhlTE3a7hsROWwZ3g/Ipq44KRovQVPvsacybUE= sha256:f3prZ+fn6mZkemcxUlgZ58qeU+OUTGWjpe9ZjFDp2LQ= End test. et art2 le cancel (ici un Supersedes, avec son propre Cancel-Lock): From: Marc SCHAEFER Subject: Supersedes: and Cancel-Key Supersedes: Message-ID: Newsgroups: alphanet.test Cancel-Lock: sha256:omdYD+yczbD2P/sFL66EWZq8mef0F1/MogtiuOOafuE= Cancel-Key: sha256:R/a5h/k9Te6XRLkmUlVdIUDYwLcj6MbbfdSFESddido= End test. Et manuellement: $ ./test-cancel-key.pl sha256:Gfz9ElhlTE3a7hsROWwZ3g/Ipq44KRovQVPvsacybUE= sha256:R/a5h/k9Te6XRLkmUlVdIUDYwLcj6MbbfdSFESddido= NOT OK $ ./test-cancel-key.pl sha256:f3prZ+fn6mZkemcxUlgZ58qeU+OUTGWjpe9ZjFDp2LQ= sha256:R/a5h/k9Te6XRLkmUlVdIUDYwLcj6MbbfdSFESddido= OK Donc, quand un Cancel-Lock est placé en entête de continuation, il ne peut être annulé par un Cancel-Key correct. Et ce sont bien des espaces 0x20.