2013-06-20 18:09:12 +02:00
|
|
|
/*
|
2014-01-02 12:00:57 +01:00
|
|
|
Copyright (c) 2007-2014 Contributors as noted in the AUTHORS file
|
2013-06-20 18:09:12 +02:00
|
|
|
|
|
|
|
This file is part of 0MQ.
|
|
|
|
|
2013-09-09 19:58:31 +02:00
|
|
|
This tool generates a CurveZMQ keypair, as two printable strings you can
|
|
|
|
use in configuration files or source code. The encoding uses Z85, which
|
|
|
|
is a base-85 format that is described in 0MQ RFC 32, and which has an
|
|
|
|
implementation in the z85_codec.h source used by this tool. The keypair
|
Added Z85 support
The use of binary for CURVE keys is painful; you cannot easily copy
these in e.g. email, or use them directly in source code. There are
various encoding possibilities. Base16 and Base64 are not optimal.
Ascii85 is not safe for source (it generates quotes and escapes).
So, I've designed a new Base85 encoding, Z85, which is safe to use
in code and elsewhere, and I've modified libzmq to use this where
it also uses binary keys (in get/setsockopt).
Very simply, if you use a 32-byte value, it's Base256 (binary),
and if you use a 40-byte value, it's Base85 (Z85).
I've put the Z85 codec into z85_codec.hpp, it's not elegant C++
but it is minimal and it works. Feel free to rewrap as a real class
if this annoys you.
2013-06-28 22:10:22 +02:00
|
|
|
always works with the secret key held by one party and the public key
|
2013-09-09 19:58:31 +02:00
|
|
|
distributed (securely!) to peers wishing to connect to it.
|
Added Z85 support
The use of binary for CURVE keys is painful; you cannot easily copy
these in e.g. email, or use them directly in source code. There are
various encoding possibilities. Base16 and Base64 are not optimal.
Ascii85 is not safe for source (it generates quotes and escapes).
So, I've designed a new Base85 encoding, Z85, which is safe to use
in code and elsewhere, and I've modified libzmq to use this where
it also uses binary keys (in get/setsockopt).
Very simply, if you use a 32-byte value, it's Base256 (binary),
and if you use a 40-byte value, it's Base85 (Z85).
I've put the Z85 codec into z85_codec.hpp, it's not elegant C++
but it is minimal and it works. Feel free to rewrap as a real class
if this annoys you.
2013-06-28 22:10:22 +02:00
|
|
|
|
2013-06-20 18:09:12 +02:00
|
|
|
0MQ is free software; you can redistribute it and/or modify it under
|
|
|
|
the terms of the GNU Lesser General Public License as published by
|
|
|
|
the Free Software Foundation; either version 3 of the License, or
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
0MQ is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU Lesser General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
2014-06-27 16:41:27 +02:00
|
|
|
#include <stdlib.h>
|
2013-09-26 11:35:52 +02:00
|
|
|
#include <assert.h>
|
2013-09-29 22:05:27 +02:00
|
|
|
#include <zmq.h>
|
2013-06-20 18:09:12 +02:00
|
|
|
|
|
|
|
int main (void)
|
|
|
|
{
|
2013-09-09 19:58:31 +02:00
|
|
|
puts ("This tool generates a CurveZMQ keypair, as two printable strings you can");
|
|
|
|
puts ("use in configuration files or source code. The encoding uses Z85, which");
|
|
|
|
puts ("is a base-85 format that is described in 0MQ RFC 32, and which has an");
|
|
|
|
puts ("implementation in the z85_codec.h source used by this tool. The keypair");
|
Added Z85 support
The use of binary for CURVE keys is painful; you cannot easily copy
these in e.g. email, or use them directly in source code. There are
various encoding possibilities. Base16 and Base64 are not optimal.
Ascii85 is not safe for source (it generates quotes and escapes).
So, I've designed a new Base85 encoding, Z85, which is safe to use
in code and elsewhere, and I've modified libzmq to use this where
it also uses binary keys (in get/setsockopt).
Very simply, if you use a 32-byte value, it's Base256 (binary),
and if you use a 40-byte value, it's Base85 (Z85).
I've put the Z85 codec into z85_codec.hpp, it's not elegant C++
but it is minimal and it works. Feel free to rewrap as a real class
if this annoys you.
2013-06-28 22:10:22 +02:00
|
|
|
puts ("always works with the secret key held by one party and the public key");
|
2013-09-09 19:58:31 +02:00
|
|
|
puts ("distributed (securely!) to peers wishing to connect to it.");
|
2013-06-20 18:09:12 +02:00
|
|
|
|
2013-09-29 22:05:27 +02:00
|
|
|
char public_key [41];
|
|
|
|
char secret_key [41];
|
2014-06-27 16:41:27 +02:00
|
|
|
if (zmq_curve_keypair (public_key, secret_key)) {
|
|
|
|
if (zmq_errno () == ENOTSUP)
|
2013-09-29 22:05:27 +02:00
|
|
|
puts ("To use curve_keygen, please install libsodium and then rebuild libzmq.");
|
|
|
|
exit (1);
|
|
|
|
}
|
2013-06-20 18:09:12 +02:00
|
|
|
|
Added Z85 support
The use of binary for CURVE keys is painful; you cannot easily copy
these in e.g. email, or use them directly in source code. There are
various encoding possibilities. Base16 and Base64 are not optimal.
Ascii85 is not safe for source (it generates quotes and escapes).
So, I've designed a new Base85 encoding, Z85, which is safe to use
in code and elsewhere, and I've modified libzmq to use this where
it also uses binary keys (in get/setsockopt).
Very simply, if you use a 32-byte value, it's Base256 (binary),
and if you use a 40-byte value, it's Base85 (Z85).
I've put the Z85 codec into z85_codec.hpp, it's not elegant C++
but it is minimal and it works. Feel free to rewrap as a real class
if this annoys you.
2013-06-28 22:10:22 +02:00
|
|
|
puts ("\n== CURVE PUBLIC KEY ==");
|
2013-09-29 22:05:27 +02:00
|
|
|
puts (public_key);
|
Added Z85 support
The use of binary for CURVE keys is painful; you cannot easily copy
these in e.g. email, or use them directly in source code. There are
various encoding possibilities. Base16 and Base64 are not optimal.
Ascii85 is not safe for source (it generates quotes and escapes).
So, I've designed a new Base85 encoding, Z85, which is safe to use
in code and elsewhere, and I've modified libzmq to use this where
it also uses binary keys (in get/setsockopt).
Very simply, if you use a 32-byte value, it's Base256 (binary),
and if you use a 40-byte value, it's Base85 (Z85).
I've put the Z85 codec into z85_codec.hpp, it's not elegant C++
but it is minimal and it works. Feel free to rewrap as a real class
if this annoys you.
2013-06-28 22:10:22 +02:00
|
|
|
|
|
|
|
puts ("\n== CURVE SECRET KEY ==");
|
2013-09-29 22:05:27 +02:00
|
|
|
puts (secret_key);
|
Added Z85 support
The use of binary for CURVE keys is painful; you cannot easily copy
these in e.g. email, or use them directly in source code. There are
various encoding possibilities. Base16 and Base64 are not optimal.
Ascii85 is not safe for source (it generates quotes and escapes).
So, I've designed a new Base85 encoding, Z85, which is safe to use
in code and elsewhere, and I've modified libzmq to use this where
it also uses binary keys (in get/setsockopt).
Very simply, if you use a 32-byte value, it's Base256 (binary),
and if you use a 40-byte value, it's Base85 (Z85).
I've put the Z85 codec into z85_codec.hpp, it's not elegant C++
but it is minimal and it works. Feel free to rewrap as a real class
if this annoys you.
2013-06-28 22:10:22 +02:00
|
|
|
|
2013-06-20 18:09:12 +02:00
|
|
|
exit (0);
|
|
|
|
}
|