From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/901 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.user Subject: Re: Supersede asks for password for canlock... Date: Fri, 09 Aug 2002 22:30:24 +0200 Message-ID: References: <27znvvrfay.fsf@chef.local> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138667774 8881 80.91.229.2 (31 Jan 2006 00:36:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:36:14 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:28:17 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: 178.230.13.217.in-addr.dgcsystems.net Original-X-Trace: quimby.gnus.org 1028926380 27013 217.13.230.178 (9 Aug 2002 20:53:00 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 9 Aug 2002 20:53:00 GMT User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu) Cancel-Lock: sha1:08Ibnc7/+8SHi1WgpL6OR0J2yQA= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:1041 Original-Lines: 40 X-Gnus-Article-Number: 1041 Tue Jan 17 17:28:17 2006 Xref: news.gmane.org gmane.emacs.gnus.user:901 Archived-At: Jan Exner writes: > I recently upgraded from Emacs 20.7/gnus 5.8.8 to Emacs 21.2/Oort gnus > 0.06. Good, please keep transition problem reports coming. Upgrading to Oort should be smooth, but I'm sure it isn't well tested. > Today, for the first time since, I tried to supersede an article and > gnus or emacs asked me for "Password for Canlock:". I have no clue > what that password might be, and those I tried ("" and my own) did not > work. This happens if you try to supersede an article with a Cancel-Lock header and you don't have a local cancel lock password configured. The cancel lock password is generated when you post, and then saved in your ~/.emacs. So there are two reasons why you didn't have a cancel lock password: 1) you didn't post the article 2) saving the cancel-lock password failed. As it happens, it was 3) the cancel-lock code uses a separate variable when verifying messages that would have been set correctly if you restarted Emacs, but not if you tried to supersede an article in the same Emacs session as the one where you ran Oort for the first time. The following has been committed. --- message.el.~6.241.~ 2002-07-26 20:04:07.000000000 +0200 +++ message.el 2002-08-09 22:22:01.000000000 +0200 @@ -3135,7 +3135,8 @@ This is the value of `canlock-password', if that option is non-nil. Otherwise, generate and save a value for `canlock-password' first." (unless canlock-password - (customize-save-variable 'canlock-password (message-canlock-generate))) + (customize-save-variable 'canlock-password (message-canlock-generate)) + (setq canlock-password-for-verify canlock-password)) canlock-password) (defun message-insert-canlock ()