[hashcash] Re: comment on reducing padding (Re: Re: libfastmint update 20040915)
- From: Atom 'Smasher' <atom@xxxxxxxxxxxxxx>
- To: hashcash@xxxxxxxxxxxxx
- Date: Thu, 16 Sep 2004 16:15:03 -0400 (EDT)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Thu, 16 Sep 2004, Adam Back wrote:
Atom writes:
thoughts (after i should be in bed) about getting rid of the padding...
hhmmm... what if the padding was done internally? instead of padding the
stamp that's output, a minting application would create a stamp _as_if_ it
were padded and a verifying application would internally add appropriate
padding before calculating the hash.
Yes I thought about this one also. However the downside is one can no
longer easily verifying a stamp in script languages using the sha1sum
utility. One first would have to undeo the padding compression.
=================
the ease (or difficulty) depends on the language and how the padding is
handled. padding doesn't have to prepend the counter, it could prepend or
append the entire stamp. in any case, awk can handle it with little
difficulty and i suspect perl can handle it too.
but if anyone is using a scripting language, they should have a hashcash
executable available to do this grunt work.
...atom
_________________________________________
PGP key - http://atom.smasher.org/pgp.txt
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
"Some folks look for answers
others look for fights,
some folks up in treetops
just looking for their kites"
-- Grateful Dead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.6 (FreeBSD)
Comment: What is this gibberish?
Comment: http://atom.smasher.org/links/#digital_signatures
iQEcBAEBCAAGBQJBSfROAAoJEAx/d+cTpVciAJ8H/iTvoPSuAThZ6hVncji3/mcg
mFQut459VBGTslafmcUiDyk4o0KG2uNiUHXJ9SjhqDWQOPMxfHoS8sbJEto9kJoL
cyyUF2b55tpyoVR7MPU5MpbZOZlonH+Qick6utcWT2CZwMDitYlqc5MV4vR4+Swk
ULLQoxd+W9H9MkkOGPGe+LhQLe/0Apw/sjvol6RFczuLjWdvlrkgwZU3ezOO9+Mn
j15zcUwV2hKk134AHX4ZhUm9DsZY6J2zz9v9QyoW5spYzqp+C9OfBNKfFPwUMYTf
3EWwlfmE8VLd5isgt9a+/uh92vyqZWHvv4OPChkTAo+1VvlHVuZ/68CfAKXIohA=
=WXQn
-----END PGP SIGNATURE-----
- Follow-Ups:
- References:
- [hashcash] libfastmint update 20040915
- From: Jonathan Morton
- [hashcash] Re: libfastmint update 20040915
- From: Atom 'Smasher'
- [hashcash] Re: libfastmint update 20040915
- From: Jonathan Morton
- [hashcash] Re: libfastmint update 20040915
- From: Atom 'Smasher'
- [hashcash] comment on reducing padding (Re: Re: libfastmint update 20040915)
- From: Adam Back
Other related posts:
- » [hashcash] comment on reducing padding (Re: Re: libfastmint update 20040915)
- » [hashcash] Re: comment on reducing padding (Re: Re: libfastmint update 20040915)
- » [hashcash] Re: comment on reducing padding (Re: Re: libfastmint update 20040915)
- » [hashcash] Re: comment on reducing padding (Re: Re: libfastmint update 20040915)
- » [hashcash] Re: comment on reducing padding (Re: Re: libfastmint update 20040915)
- » [hashcash] Re: comment on reducing padding (Re: Re: libfastmint update 20040915)
- » [hashcash] Re: comment on reducing padding (Re: Re: libfastmint update 20040915)
thoughts (after i should be in bed) about getting rid of the padding...
hhmmm... what if the padding was done internally? instead of padding the stamp that's output, a minting application would create a stamp _as_if_ it were padded and a verifying application would internally add appropriate padding before calculating the hash.
Yes I thought about this one also. However the downside is one can no longer easily verifying a stamp in script languages using the sha1sum utility. One first would have to undeo the padding compression.
...atom
- [hashcash] libfastmint update 20040915
- From: Jonathan Morton
- [hashcash] Re: libfastmint update 20040915
- From: Atom 'Smasher'
- [hashcash] Re: libfastmint update 20040915
- From: Jonathan Morton
- [hashcash] Re: libfastmint update 20040915
- From: Atom 'Smasher'
- [hashcash] comment on reducing padding (Re: Re: libfastmint update 20040915)
- From: Adam Back