On Mon, Oct 12, 2020, 6:46 PM Stefan Claas <[1]sac@300baud.de> wrote:

     Stefan Claas wrote:
     > Karl wrote:
     >
     > > I embarrassingly haven't sustained much understanding of golang
     ... I
     > > wanted to convert my box keys to signify-nacl keys but it seems
     the
     > > formats are different; my own signature doesn't verify when I
     just
     > > copy the bytes.
     >
     > NaCl sign secret keys are 64 bytes, while NaCl box secret keys are
     32 bytes.
     Since you are a Programmer, maybe this helps:
     <[2]https://crypto.stackexchange.com/questions/54353/why-are-nacl-se
     cret-keys-64-bytes-for-signing-but-32-bytes-for-box>

   Quote:
   An Ed25519 private key consists of a 32 byte seed (from which you can
   cheaply derive the 32 byte private scalar and the 32 byte hash prefix)
   and the 32 byte public key.
   This is actually what I tried, but I think I need to look at the
   implementations to make it work.  I can likely figure the golang out if
   I need to, or probably there's a more direct approach to the whole
   shebang.  Maybe I'll come up with a high latency message to send to
   your offline system =)
   -sent from my closed source toosmartphone, which is dangerously rotting
   the flesh of my hands

     Regards
     Stefan
     --
     NaClbox:
     cc5c5f846c661343745772156a7751a5eb34d3e83d84b7d6884e507e105fd675
       The computer helps us to solve problems, we did not have without
     him.

References

   1. mailto:sac@300baud.de
   2. https://crypto.stackexchange.com/questions/54353/why-are-nacl-secret-keys-64-bytes-for-signing-but-32-bytes-for-box