kaniini/ecdsatool

ECDSA-CHALLENGE keypair manipulation tools and library

ecdsatool's Issues

Copyright clarification

About the possibility of adding libecdsaauth support in an irc client, i would like to understand if the library is

Copyright (c) 2005-2013 Atheme Project (http://www.atheme.org)

as stated in the CHANGES file, or

Copyright (c) 2013 William Pitcock [email protected].

as stated in the README.md file.

generates malformed keys

@maxteufel can probably provide more detailed information.

2015-01-03 22:17:16+0200 < Mikaela> mt: that pull request prevents my bot from connecting to freenode now that I enabled it, it tracebacks and I am pasting it
2015-01-03 22:18:06+0200 < MetaNova> Limnoria: version
2015-01-03 22:18:23+0200 < MetaNova> no?
2015-01-03 22:18:26+0200 < MetaNova> @version
2015-01-03 22:18:27+0200 <@Limnoria> The current (running) version of this Supybot is 0.83.4.1+limnoria 2014.12.11, running on Python 3.4.2 (default, Dec  2 2014, 15:08:18)  [GCC 4.9.2].  The newest versions available online are 2015.01.03 (in testing), 2014.12.22 (in master).
2015-01-03 22:18:31+0200 < Unit193> @latency
2015-01-03 22:18:32+0200 <@Limnoria> 0.05 seconds.
2015-01-03 22:18:39+0200 < tacocat> not all bots respond to their nick
2015-01-03 22:23:06+0200 <@Limnoria> Mikaela just pasted ecdsa prevents connecting to freenode (type: pytb): http://supybot.aperio.fr/paste/VhHs4ZdI
2015-01-03 22:23:11+0200 < Mikaela> mt: ^^^
2015-01-03 22:23:42+0200 < tacocat> ಠ_ಠ
2015-01-03 22:24:14+0200 < Mikaela> ?
2015-01-03 22:26:21+0200 < Mikaela> after unsetting the variable, the bot connects without issues. it responds to msb1 on #limnoria-bots
2015-01-03 22:26:37+0200 < pinkieval> seriously?!?!
2015-01-03 22:26:38+0200 < mt> looks like a malformed ec key - oh, and it looks like you forgot to strip the password (self.sasl_password = '...')
2015-01-03 22:27:02+0200 < pinkieval> why does it happen every time I merge a pull request related to SASL?
2015-01-03 22:27:07+0200 < tacocat> lool
2015-01-03 22:27:23+0200 < tacocat> pinkieval: sasl is evil and wants to take over the world
2015-01-03 22:27:36+0200 < pinkieval> seriously, test your code
2015-01-03 22:27:40+0200 < Mikaela> DEBUG 2015-01-03T20:27:22 supybot Incoming message (freenode): :NickServ!NickServ@services. NOTICE Euforia :The password for Dysforia has been changed to
2015-01-03 22:27:40+0200 < Mikaela> I never learn this
2015-01-03 22:27:44+0200 < pinkieval> I know it's a pain to test code live
2015-01-03 22:27:57+0200 < Mikaela> it doesn't happen every time and this is why there is testing branch
2015-01-03 22:28:07+0200 < mt> I actually tested my code and it worked fine
2015-01-03 22:28:13+0200 < pinkieval> at least it does not affect people who don't use SASL this time
2015-01-03 22:28:21+0200 < Mikaela> mt: the key was created using ecdsatool keygen
2015-01-03 22:29:02+0200 < Mikaela> it only affects people who set that configuration variable
2015-01-03 22:29:02+0200 < Mikaela> and the SASL timeout bug still affects everyone who uses any SASL mechanism including EXTERNAL/CertFP (as Limnoria automatically attempts EXTERNAL when certfp is configured)
2015-01-03 22:29:31+0200 < Mikaela> 2015-01-03 22:29:19+0200 < Euforia> The current (running) version of this Supybot is 0.83.4.1+limnoria 2015.01.03, running on Python 3.4.2 (default, Oct 13 2014, 19:49:42)  [GCC 4.2.1 Compatible Debian Clang 3.0 (tags/RELEASE_30/final)].  The newest versions available online are 2015.01.03 (in testing), 2014.12.22 (in master).
2015-01-03 22:29:46+0200 < mt> can you create one with `openssl ecparam -name prime256v1 -genkey -out <file>` and the get the fingerprint with `ecdsatool pubkey <file>` and test that?
2015-01-03 22:30:04+0200 < Mikaela> probably
2015-01-03 22:33:01+0200 < Mikaela> mt: that worked, but ecdsatool not working directly is an issue as every document tells to use it for generating the key
2015-01-03 22:34:38+0200 < mt> it's most likely an ecdsatool issue then
2015-01-03 22:35:03+0200 < Mikaela> while ecdsatool is the official way for creating the key?
2015-01-03 22:35:13+0200 < mt> "official way"?
2015-01-03 22:35:37+0200 < Mikaela> the one which every documentation that I can currently find recommends (mainly README for the said project)
2015-01-03 22:36:00+0200 < mt> there's nothing saying that it is the official way; atheme should support every valid prime256v1 keypair
2015-01-03 22:36:18+0200 < Mikaela> you might probably want to open an issue to ecdsatool then
2015-01-03 22:43:59+0200 < Mikaela> it appears that I also broke SASL PLAIN by that password change, but I can probably ignore it

add support for passphrase-encrypted keys (to both library and ecdsatool)

topic pretty much covers it. not really important since most clients don't support passphrase-encrypted certs either, but it would be nice.

cap_sasl.pl does not identify on reconnect on freenode

i am using the cap_sasl.pl script provided by ecdsatool with irssi to connect to freenode. it identifies properly on the initial connect but fails to identify on reconnects. am i doing something wrong or is this a known issue? thanks for all your hard work on ecdsatool.