I've slightly changed a part of the message that didn't hold too much meaning. ``` $ export PATH=$HOME/go/bin:"$PATH" $ box add-peer -name stefan-test -key 688fc978029e4bd309eaebea1e139ee6c461e08e19b714264dd91fbb62f5ca7c $ base64 -d | box open -from stefan-test AgAAAHYwSAAAAO+xQIT5meBNroABRxnwz1nF8Apub/z5OiqCftZUpGTBbcejwe6XQF4lpAnhW9YG NAl9/zdLkj8FOG2NQmhbx82HXJv1Ju2c1w== Hello, Karl :-) Regards Stefan ``` ``` $ box seal -to stefan-test | base64 Note: reading payload from stdin Stefan, I got: AgAAAHYwSAAAAO+xQIT5meBNroABRxnwz1nF8Apub/z5OiqCftZUpGTBbcejwe6XQF4lpAnhW9YG NAl9/zdLkj8FOG2NQmhbx82HXJv1Ju2c1w== from you. Is this the same encrypted message as the one you sent? I'm expecting that it is. <here i hit ctrl-D to terminate input> ``` ``` AgAAAHYwNwAAACYoBMBoexWybVHaD6gSUYQvDho9F4ptZ5/fwtJrejNmwpXToWN2YtBqg3v6886R QsxcjqLBKxZ1AAAAZhsWlHZ+bZ2/DL7v+1IdT9m1xMl18QCigsZEbLovKiYMpddxBnqGgF4MeTX6 ptxfE8duAZQ3+wc+ij+Z1TmZScTHd9bxcGlkn0aj2nfuaFDFRP/fm3I50iL6QwXpNyMKD8Oj2+5k RIfQpn2OxScgn6wauUL1TQAAADacCd0xdLntxPiQU+LdyX+QexJkw8ZTZHPy3HkfuxKkQfwYLqX1 zMD8uOuP1mJ911dhbnnOEiYADkkeAJnDpp9TQD1PFV6wRhr5eRtJhgAAALgpH0r16Fkri92M4JPN XfJNkW0PMnBpuUY2DTvP+gHKYLQAU7m5BQ9JkG5rU70/YQeWGHYn8BU40TVwj8o+FbPhuIer5qIq hYj3v2cZVv6hCYdyj2bDuy1qBtqU+bBResYI9zFRTgWtpeiWJukKu921Bg9zZ9rqKkzcAI5h/wDe 6pVx6NCF ``` If I had sent a nacl-encrypted message to Stefan out of the blue, he might have gotten excited to have received an encrypted message, and accessed his offline machine to read it and reply. On 10/12/20, Stefan Claas <sac@300baud.de> wrote:
Stefan Claas wrote:
Karl wrote:
Error: Command required $ ~/go/bin/box new-identity $ ~/go/bin/box list NAME KIND PUBLIC KEY self identity c72e81da09e333bc8804205bcfcf3bd8821cad61ad862d57114339e5ee00a664 $ ~/go/bin/box add-peer -name stefan -key cc5c5f846c661343745772156a7751a5eb34d3e83d84b7d6884e507e105fd675 $ ~/go/bin/box seal -to stefan > message.sealed Stefan: did you get this? [Ctrl-D to terminate entry] # I also changed something minor in the encrypted message, to support private communication. $ xxd -ps message.sealed 0200000076304200000031c2f6d6329d2d26347613cb5e9c8f3e1848b707 9fcf674e0b744be30741f434f09490db0979b027825fc649d1cde868293d 078aba0045b435e25859e8b8814d7658
Stefan, 0200000076304200000031c2f6d6329d2d26347613cb5e9c8f3e1848b707 9fcf674e0b744be30741f434f09490db0979b027825fc649d1cde868293d 078aba0045b435e25859e8b8814d7658 ?
- karl's-rhel7ae25thinkpad-that-mysteriously-freezes-up-when-he-leaves-it-online, naclbox c72e81da09e333bc8804205bcfcf3bd8821cad61ad862d57114339e5ee00a664
In order to send me a message you would have to include your name too.
$ box seal -from Karl -to Stefan <MESSAGE >SEALED, which then writes a binary authenticated encrypted blob and which I could only open then if I would be in possession of your pub key. It is also advised when you send me such message that you consider to base64 etc. encode it, prior sending/posting.
BTW. my key is currently on my offline computer which I am not using now, because I am a bit busy with other things on my online computer.
Ouch, just overlooked that you created a key, sorry!
$ box add-peer -name Karl -key c72e81da09e333bc8804205bcfcf3bd8821cad61ad862d57114339e5ee00a664
A *test* key of mine you can use: 688fc978029e4bd309eaebea1e139ee6c461e08e19b714264dd91fbb62f5ca7c
a test message for you, additionally base64 encoded:
AgAAAHYwSAAAAO+xQIT5meBNroABRxnwz1nF8Apub/z5OiqCftZUpGTBbcejwe6XQF4lpAnhW9YG NAl9/zdLkj8FOG2NQmhbx82HXJv1Ju2c1w==
Regards Stefan
-- NaClbox: cc5c5f846c661343745772156a7751a5eb34d3e83d84b7d6884e507e105fd675 The computer helps us to solve problems, we did not have without him.