| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
This also includes a necessary API refactoring of crypto from IDENTITY
to UTIL.
|
| |
|
|
| |
gnunet_private_config.h insanity
|
| |
|
|
|
|
|
|
|
|
|
| |
This change allows third party programs to use gnunet either with the
platform header from the sources used to build to gnunet, or use their
own platform header by defining GNUNET_CUSTOM_PLATFORM_H which will be
included in its stead.
This also means that programs no longer must include "platform.h" (or
similar) manually.
The change (should be) backwards compatible to some degree.
Fixes #4615
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The function GNUNET_CRYPTO_eddsa_key_from_file returns now
- GNUNET_OK on success,
- GNUNET_NO if do_create was set but we found an existing file,
- GNUNET_SYSERR on failure _or_ if the file didn't exist and
do_create was not set
Fixes #7106
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hi,
find attach the patch which makes all 3 test cases work with Ed25519.
There are some minor hacks in the test cases to allow enabling of
Libgcrypt debugging and also some minor output style changes.
There is one FIXME in the code:
/* FIXME: mpi_print creates an unsigned integer - is that intended
or should we convert it to a signed integer (2-compl)? */
mpi_print (xbuf, sizeof (xbuf), result_x);
X may be positive or negative but GCRYMPI_FMT_USG ignores the sign.
Thus this is not what we actually want. Should we change it to 2-comp
(GCRYMPI_FMT_STD) so that we have a proper value? Given that the curve
is 255 bit this should alwas fit int the 256 bit buffer. Another option
would be to use the EdDSA method for the sign but that is optimized to
easily recover x and would be more work. Or we store the sign in the
high bit. t all depends on what you want to write into the protocol
specs.
I would also like to revert the way we distinguish between Ed25519 with
and without ECDSA: The way we do it right now is by assuming the
Ed25519 is always used with EdDSA unless a flag has been set. This is a
bit surprising and requiring the "(flags eddsa)" would be a less
surprising interface.
Salam-Shalom,
Werner
|
| |
|
