[hashcash] and hashcash-0.32 (Re: hashcash-sendmail bug fixes.)

  • From: Adam Back <adam@xxxxxxxxxxxxxxx>
  • To: hashcash@xxxxxxxxxxxxx
  • Date: Fri, 9 Apr 2004 18:41:07 -0400

On Fri, Apr 02, 2004 at 05:05:43PM -0600, Kyle Hasselbacher wrote:
> I noticed a bug that would make the daemon hang sometimes, and I
> think I fixed it.

Well I'm using the latest hashcash-sendmail and the latest (just
released!) hashcash and it seems to work for me.

Right after reading your bug report I realised a logic problem with
wildcards in the then just released 0.31.  I also just released a new
version of hashcash (0.32) which allows the user to control the
semantics so they can get the right behavior.  

The problem with wildcard addresses was as follows:

If I want to receive mail as adam@xxxxxxxx requiring 15 bits, and for
*@dev.null requiring 10 bits, then that means I probably do NOT want
to accept mail to adam@xxxxxxxx when there are only 10 bits.

So there is now a new option -o to allow you to specify which resource
overrides which other resource.  From the updated man page:

        For example this: -b15 -r adam@xxxxxxxx -o -b10 *@dev.null
        states that mail to address adam@xxxxxxxx requires 15 bits,
        but mail to *@dev.null requires only 10 bits.  If we omitted
        the -o override relationship between the two resources, a
        stamp of 10 bits would be accepted for address adam@xxxxxxxx
        because while it would be rejected as having insuffi- cient
        bits under the first rule, it would be accepted under the 2nd
        rule.  The -o option allows you avoid this problem.

The new rpm also is signed which the last few weren't.

Anyone want to check the new regexp stuff compiles on different unixen
and (been a few versions now) windows?

Adam

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 

Other related posts:

  • » [hashcash] and hashcash-0.32 (Re: hashcash-sendmail bug fixes.)