support detection of newer standards (EdDSA, issuer fingerprint), and minor cleanup #21
Conversation
If we're OK with "passing" on experiemntal algorithms, we should be ok with passing on known algorithms that we know the name of but don't implement.
The issuer fingerprint effectively supercedes issuer keyID as a more robust signal of the issuer (though it's possible and in some cases likely to include both in a signature, to ensure that it's understood by old and new code).
|
any word on this? these changes make it possible to do real work with this package. without that, there are regular failures due to exceptions being thrown on unknown algorithms. |
|
I don't feel like @toofishes is going to merge anything. At least there is a long unresponsiveness. But I would be glad if he would find some time! I did some extensive stuff here (regarding decryption of key material and support for ECC keys). We may can join forces :) |
|
@dkg or @alex-nitrokey - I would be happy to transfer ownership of this project and the python package to one of you! I no longer have time (or the need) to maintain this project, unfortunately. |
|
Hey @toofishes, actually I would be interested in doing so, but in this case I would prefer to move it to @Nitrokey right away, because this is the company I am doing the patches for. If you are fine with this as well, we might talk about the details? You can reach me via alex @ nitrokey dot com or look here and write to the support address. |
|
I'd be willing to assist in any way that can get the PyPI release version updated, as forking for that purpose seems unnecessary given creator's willingness to handover maintenance to community. |
No description provided.