Skip to content
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

feat: set the correct cipher suite when claiming key packages #2742

Conversation

MohamadJaara
Copy link
Member

@MohamadJaara MohamadJaara commented May 6, 2024


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

Claims key packages does not set the correct cipher suite to the backend

Solutions

set the correct cipher suite when claiming key packages

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

Needs releases with:

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

Copy link
Contributor

github-actions bot commented May 6, 2024

Test Results

2 865 tests   2 742 ✔️  31s ⏱️
   491 suites     123 💤
   491 files           0

Results for commit aa93b98.

♻️ This comment has been updated with latest results.

@datadog-wireapp
Copy link

datadog-wireapp bot commented May 6, 2024

Datadog Report

Branch report: feat/set-the-correct-cipher-suite-when-claiming-key-packeges
Commit report: 23afcee
Test service: kalium-jvm

✅ 0 Failed, 2883 Passed, 107 Skipped, 8m 57.04s Wall Time

…correct-cipher-suite-when-claiming-key-packeges
@MohamadJaara MohamadJaara changed the base branch from release/android-cycle-4.6 to fix/fetch-MLS-config-when-not-avilable-locally May 6, 2024 11:45
…correct-cipher-suite-when-claiming-key-packeges

# Conflicts:
#	cryptography/src/commonJvmAndroid/kotlin/com.wire.kalium.cryptography/CoreCryptoCentral.kt
#	logic/src/commonJvmAndroid/kotlin/com/wire/kalium/logic/CoreCryptoExceptionMapper.kt
Signed-off-by: MohamadJaara <[email protected]>
…ly' into feat/set-the-correct-public-key-when-creating-MLS-conversation

# Conflicts:
#	gradle/libs.versions.toml
…ly' into feat/set-the-correct-public-key-when-creating-MLS-conversation
@MohamadJaara MohamadJaara changed the base branch from fix/fetch-MLS-config-when-not-avilable-locally to feat/set-the-correct-public-key-when-creating-MLS-conversation May 6, 2024 22:36
…g-MLS-conversation' into feat/set-the-correct-cipher-suite-when-claiming-key-packeges

# Conflicts:
#	cryptography/src/commonJvmAndroid/kotlin/com.wire.kalium.cryptography/CoreCryptoCentral.kt
#	cryptography/src/jvmTest/kotlin/com/wire/kalium/cryptography/BaseProteusClientTest.kt
#	logic/src/commonTest/kotlin/com/wire/kalium/logic/client/E2EIClientProviderTest.kt
Copy link
Contributor

@mchenani mchenani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Base automatically changed from feat/set-the-correct-public-key-when-creating-MLS-conversation to release/android-cycle-4.6 May 7, 2024 10:03
…-correct-cipher-suite-when-claiming-key-packeges

# Conflicts:
#	cryptography/src/commonJvmAndroid/kotlin/com.wire.kalium.cryptography/MLSClientImpl.kt
#	logic/src/commonMain/kotlin/com/wire/kalium/logic/data/conversation/MLSConversationRepository.kt
#	logic/src/commonMain/kotlin/com/wire/kalium/logic/data/mlspublickeys/MLSPublicKeysMapper.kt
#	logic/src/commonMain/kotlin/com/wire/kalium/logic/data/mlspublickeys/MLSPublicKeysRepository.kt
#	logic/src/commonTest/kotlin/com/wire/kalium/logic/client/E2EIClientProviderTest.kt
@MohamadJaara MohamadJaara enabled auto-merge (squash) May 7, 2024 10:15
@MohamadJaara MohamadJaara merged commit 2bcb288 into release/android-cycle-4.6 May 7, 2024
17 checks passed
@MohamadJaara MohamadJaara deleted the feat/set-the-correct-cipher-suite-when-claiming-key-packeges branch May 7, 2024 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants