Mercurial > dropbear
view ecc.h @ 1227:5dde22e8a189
scp: Have `fatal()' append a newline to the message
Date: Wed, 4 Nov 2015 20:33:19 -0000
It would seem that it's standard practice not to include a newline in the message
text, but that results in poor formatting, as a shell's command line then begins
on the line of the error message itself.
This commit simply instructs `fatal()' to append a newline after the message,
which should be suitable behavior for all of the invocations I've come across.
author | Michael Witten <mfwitten@gmail.com> |
---|---|
date | Tue, 19 Jan 2016 00:23:19 +0800 |
parents | 4f3335bba3d9 |
children | 9169e4e7cbee |
line wrap: on
line source
#ifndef DROPBEAR_DROPBEAR_ECC_H #define DROPBEAR_DROPBEAR_ECC_H #include "includes.h" #include "options.h" #include "buffer.h" #ifdef DROPBEAR_ECC struct dropbear_ecc_curve { int ltc_size; /* to match the byte sizes in ltc_ecc_sets[] */ const ltc_ecc_set_type *dp; /* curve domain parameters */ const struct ltc_hash_descriptor *hash_desc; const char *name; }; extern struct dropbear_ecc_curve ecc_curve_nistp256; extern struct dropbear_ecc_curve ecc_curve_nistp384; extern struct dropbear_ecc_curve ecc_curve_nistp521; extern struct dropbear_ecc_curve *dropbear_ecc_curves[]; void dropbear_ecc_fill_dp(); struct dropbear_ecc_curve* curve_for_dp(const ltc_ecc_set_type *dp); /* "pubkey" refers to a point, but LTC uses ecc_key structure for both public and private keys */ void buf_put_ecc_raw_pubkey_string(buffer *buf, ecc_key *key); ecc_key * buf_get_ecc_raw_pubkey(buffer *buf, const struct dropbear_ecc_curve *curve); int buf_get_ecc_privkey_string(buffer *buf, ecc_key *key); mp_int * dropbear_ecc_shared_secret(ecc_key *pub_key, ecc_key *priv_key); #endif #endif /* DROPBEAR_DROPBEAR_ECC_H */