Gnus development mailing list
 help / color / mirror / Atom feed
From: "Matt Armstrong" <matt+dated+1007224448.7bca4c@lickey.com>
Cc: ding@gnus.org
Subject: Re: cancel locks
Date: Thu,  1 Nov 2001 09:34:09 -0700 (MST)	[thread overview]
Message-ID: <20011101163409.39F32BD4F@squeaker.lickey.com> (raw)
In-Reply-To: <rjvgguzop1.fsf@ssv2.dina.kvl.dk> (Per Abrahamsen's message of "Thu, 01 Nov 2001 12:59:54 +0100")

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Florian Weimer <fw@deneb.enyo.de> writes:
>
>> I'm sorry, but it's rather straightforward to guess a password
>> generated by 'message-unique-id'.
>
> Yes, but you need to read and understand the code in message to do
> so, and you need google to track down the users first message to get
> the necessary information (from the data and message-id headers).
> That is a lot more work than faking a cancel of an unlocked message.
>
> If someone later wants to contribute a better password generator, it
> can be installed with no problem.

Here is my contribution:

(defun gnus-random-cancel-lock-password ()
  (random t)
  (format "%x%x" (random) (random)))

:-)
  
-- 
matt



  reply	other threads:[~2001-11-01 16:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 17:45 Simon Josefsson
2001-10-31 18:11 ` Bjørn Mork
2001-10-31 19:06   ` Simon Josefsson
2001-11-01  0:13     ` Robin S. Socha
2001-11-01 11:28     ` Florian Weimer
2001-11-01  8:23 ` Per Abrahamsen
2001-11-01 11:34   ` Florian Weimer
2001-11-01 11:59     ` Per Abrahamsen
2001-11-01 16:34       ` Matt Armstrong [this message]
2001-11-01 17:21         ` Per Abrahamsen
2001-11-01 17:41         ` Jesper Harder
2001-11-01 17:23           ` Simon Josefsson
2001-11-01 18:47             ` Matt Armstrong
2001-11-01 21:09               ` Florian Weimer
2001-11-01 21:10             ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011101163409.39F32BD4F@squeaker.lickey.com \
    --to=matt+dated+1007224448.7bca4c@lickey.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).