Re: [Taler] Matching crypto implementation

[Christian Grothoff]

Dear Lukas,

First of all, you might want to know that Bernd Fix is trying something
similar, re-implementing the GNUnet primitives in Go.  So you might want
to join forces on that.

Also, you should note that we don't use the original Crockford base32
encoding, but a variation where U=V (so you can spell FUCK, which
Crockford wanted to make impossible).  IIRC Bernd mentioned that we also
use a different ordering of the letters or something else 'particular',
so that might also be causing you grief. That said, AFAIK Bernd did have
"something" working, but I don't recall where his repo is (IMO such
bindings/adapters/reimplementations belong into a Gitolite repo on
gnunet.org (or taler.net), just so that they are easier to find and I'm
happy to set one up.)

Happy hacking!

Christian

On 12/25/18 6:05 PM, Lukas Großberger wrote:
> Hi fellow Taler enthusiasts,
> 
> as a long time lurker, being curious and excited about Taler from a
> distance, I finally made the leap and for the past couple of days I've
> tried to figure out the binary-compatible crypto implementations for the
> Taler basics in other languages (Go & Python). To get acquainted with
> the code base, I am trying to port a subset of the wallet features to a
> wallet implementation in a language I'm more comfortable with than
> Typescript.
> However, I found myself to struggle a lot with figuring out the exact
> steps that are for example required for the simplest encoding and hash
> test the Exchange API offers[1]. I tried to follow the code path until
> the Emscripten bindings to figure out the data types used as well as the
> function signatures. However, I suspect that something is going wrong
> when converting strings of Crockford Base32 encoded input to a byte
> representation, and converting the byte representation of the SHA512
> hash back to something Crock encodable.
> Anyway, does someone of you have insights about how to approach such an
> endeavor effectively? I'm also looking for general advice, unspecific to
> the particular first attempt I described above.
> 
> Cheers, Lukas
> 
> [1]https://docs.taler.net/api/api-exchange.html#post--test-base32
>

signature.asc
Description: OpenPGP digital signature