Changes to crypto_box and README; added crypto_generichash, crypto_scalarmult, crypto_sign

That's a good question. I pulled your branch and updated to libsodium 0.7.1
(and updated your changes locally) and... it worked just fine. Perhaps the
symbols weren't in the 0.7.0 release? Which OS are you on? If you are on
Linux (and I think Mac OS) are you familiar with the 'nm' command? You can
check like this:

nm libsodium.a | grep sign_ed25519_pk_to_curve25519

If it shows up with a 'T' that means it's in the text pages and should link
ok.  If you are on Windows you can use the 'dumpbin /exports' command to do
the same.

BTW, I had not seen the additions of the Edwards-to-curve 25519 conversion
routines. That's very cool. I had played with a .Net port that included
such commands, but decided I wanted to use Go instead so I gave up on them.


On Mon, Sep 15, 2014 at 1:48 PM, Graham Smith <notifications@github.com>
wrote:

> In sodium/crypto_box.go:
>
> >
> > -    return int(C.crypto_box_open(
> > -        (*C.uchar)(&messageOut[0]),
> > -        (*C.uchar)(&cypherText[0]), (C.ulonglong)(len(cypherText)),
> > -        (*C.uchar)(&nonce[0]),
> > -        (*C.uchar)(&pk[0]),
> > -        (*C.uchar)(&sk[0])))
> > +func BoxEasy(cypherTextOut []byte, message []byte, nonce, pk, sk []byte) int {
> > +	checkSize(cypherTextOut, len(message), "cypher text output")
>
> Any idea why crypto_sign isn't working from the package sodium? I'm new to
> Go and not sure why it's functions aren't exporting.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jasonmccampbell/GoSodium/pull/3/files#r17561047>.
>