13 Commits

Author	SHA1	Message	Date
Peter Surda	7deb7c3d4f	Typo	2017-06-10 10:11:50 +02:00
Peter Surda	bea675f9a6	Remove unnecessary "print" from previous commit	2017-03-02 15:09:01 +01:00
Peter Surda	53657dba47	Phase 1 of SHA256 support ... - new variable "digestalg" which defaults to "sha1", but allows "sha256" for those who want to sign using this - Addresses #953	2017-03-02 15:03:08 +01:00
Peter Surda	6778d6046f	Add OpenSSL 1.1.0 compatibility ... - thanks to Wolfgang Frisch <wfr@roembden.net>	2017-01-13 12:02:34 +01:00
mirrorwish	a7ec4c0555	Some preparations for python 3	2016-05-02 15:00:25 +02:00
Jonathan Warren	6ebf8666dc	support SHA256 signatures	2015-03-27 15:25:32 -04:00
Jonathan Warren	642c5858f4	handle OpenSSL.EC_KEY_get0_group() exception	2015-02-06 16:31:23 -05:00
Jonathan Warren	c306062282	Bitmessage Protocol Version Three	2014-08-27 03:14:32 -04:00
Jonathan Warren	a2a7edc9be	resolve merge conflict	2014-07-14 19:29:47 -04:00
bmng-dev	be5ab22d16	Fix name error	2014-06-08 14:07:28 +00:00
bmng-dev	9b40838f25	Use pointMult instead of arithmetic.privtopub ... pointMult is faster than the pure python arithmetic.privtopub Additionally in makeCryptor the call to a.privtopub could have just simply be changed to call the local privToPub but then privkey would have been dehexified twice (once in makeCryptor, then again in privToPub) and privToPub would have hexified its result only for makeCryptor to immediately dehexify it. This sort of unnecessary hexifying/dehexifying seems to occur throughout PyBitmessage.	2014-05-21 11:08:15 +00:00
bmng-dev	ecf78801bf	Move pointMult function to highlevelcrypto ... Copy pointMult function from class_addressGenerator.py to highlevelcrypto.py	2014-05-21 09:59:08 +00:00
fuzzgun	b79d1e93f5	Debian packaging	2013-04-01 20:23:32 +01:00