-
Notifications
You must be signed in to change notification settings - Fork 3
preview fully integrated encryption #217
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
base: develop
Are you sure you want to change the base?
Conversation
vck/src/commonMain/kotlin/at/asitplus/wallet/lib/agent/KeyMaterial.kt
Outdated
Show resolved
Hide resolved
vck/src/commonMain/kotlin/at/asitplus/wallet/lib/jws/JwsService.kt
Outdated
Show resolved
Hide resolved
54c855e
to
3c5ba7b
Compare
someone should really test this in the app. Just be sure, to also set the key agreement flag for EC key generation and delete the old holder key! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks clean
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it
then we just have to wait for @iaik-jheher to find the time to review the signum PR |
3c5ba7b
to
8f03c0e
Compare
Badum-Tsss! |
I did not yet get to testing it in the app, because first, we'll need snapshot releases of all credentials due to breaking changes in signum and I cannot make any guarantees to get to it before easter, but I will try to at least release the credentials with some distinctive version string as snapshots so testing becomes possible |
not much left of the cryptoservice. We could use this state to test encryption and key agreement on iOS, even before publishing signum. Maybe we should, because this way we could still catch any mishaps in signum before we merge there.
Opinions, anyone? @md4096?