-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[suggestion] Stop encoding X25519 keys as Ed25519 #4174
Labels
crypto
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
QA-confirmed
This bug is reproduced and needs a fix
Refactor
Improvement to overall code quality
Security
This issue asks for improved security
Comments
Arjentix
added
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
Refactor
Improvement to overall code quality
Security
This issue asks for improved security
labels
Dec 25, 2023
5 tasks
also consider this comment when handling this issue |
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 12, 2024
Signed-off-by: Daniil Polyakov <[email protected]>
5 tasks
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 13, 2024
Signed-off-by: Daniil Polyakov <[email protected]>
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 13, 2024
Signed-off-by: Daniil Polyakov <[email protected]>
Arjentix
added a commit
to Arjentix/iroha
that referenced
this issue
Feb 14, 2024
Signed-off-by: Daniil Polyakov <[email protected]>
Arjentix
added a commit
that referenced
this issue
Feb 14, 2024
Signed-off-by: Daniil Polyakov <[email protected]>
Regarding testing I suggest just to check that network works as expected |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
crypto
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
QA-confirmed
This bug is reproduced and needs a fix
Refactor
Improvement to overall code quality
Security
This issue asks for improved security
While looks like it works fine I suggest refactoring that part to make it more clear.
Currently two completely different types are casted between each other in completely implicit and silent way. I suggest to make it clear that X25519 is used only for exchanging purposes.
The text was updated successfully, but these errors were encountered: