Closed ntadej closed 1 year ago
@ntadej, @Youw, do you see any chance to proceed with this PR? Thanks.
The reason why I am asking is, that I have created Java bindings for WinSparkle and we want to use these to update Cryptomator on Windows, that securely stores vaults in cloud services.
I am planning to, but Windows is currently at the bottom of priority list for my project.
I think I've fixed the issues identified by @Youw in https://github.com/geraldcombs/winsparkle/tree/eddsa-updates. The only outstanding issue is that SignatureVerifier::VerifyEdDSAPubKey is still a placeholder. I think the proper fix would be to add a corresponding function to the ed25519 public API.
@ntadej if my changes look OK to you, feel free to grab them and add them to this PR (and assign yourself authorship if you'd like). Otherwise I'd be happy to open a separate PR.
@geraldcombs Thanks!
The only outstanding issue is that SignatureVerifier::VerifyEdDSAPubKey is still a placeholder. I think the proper fix would be to add a corresponding function to the ed25519 public API.
Let's make this simpler: VerifyEdDSAPubKey
has little usefulness and the verification is done at signature checking time anyway, so we can either just remove this part or do what was initially suggested:
Public key verfication is not there yet, I guess it is enough to just do the Base64 decoding + size check?
Otherwise I'd be happy to open a separate PR.
Oh, sorry, forgot to say: please do.
Yes, sorry for lack of activity here. I also propose you open a separate PR so it will be easier to iterate for you.
Oh, sorry, forgot to say: please do.
Done in #254.
→ #254
Add preliminary EdDSA validation support (partially closes #187 as signing is still missing). I tested with valid and invalid signature and it seems to work. Note that more testing is probably needed.
Some comments:
Tagging @kornelski and @vslavik.