On Fri, Feb 14, 2014 at 11:11 AM, Felix Fietkau <n...@openwrt.org> wrote: > The bloat increase seems a bit excessive for a minor update. Any way to > make the new stuff optional (and disabled by default)? Here are the first few lines of a diff of 'nm --size-sort' between 2013.59 and 2013.62. First column is function size.
+00000bb0 T curve25519_donna 00000b38 T sink +00000a30 t fproduct +00000944 T ltc_ecc_projective_add_point 00000734 T refresh_progress_meter -0000069c T svr_auth_pubkey +000006a0 T svr_auth_pubkey +0000068c t main_noinetd +00000680 T recv_msg_kexdh_reply 00000670 T cli_getopts -00000634 t main_noinetd -000005c8 T recv_msg_kexdh_reply -00000588 T svr_getopts +0000063c T ltc_ecc_projective_dbl_point +000005ec t fsquare +000005c4 T ltc_ecc_mul2add +000005a4 T svr_getopts 00000580 T scp_main 00000580 T mp_div Looks like most of the growth is in new ECC support functions, with some small growth to existing functions. Curve25519 is the largest single contributor at 3 kB. Disabling Curve25519 brings the final binary size to 189,900 bytes. I'm personally very interested in ECC support, I have a hardware security key that stores ECDSA key pairs, that I want to use for authentication. I'm also interested in keeping as small a diff from upstream as possible. :-) What do you think about ECC support in OpenWrt dropbear in the long term? Any ideas for reducing binary size while maintaining ECC support? _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
