Modify UnifiedPush post request to be AND_3 compliant #804
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hazematman
force-pushed
the
fix_unified_push
branch
from
7f6e94a to
1573101
Compare
aberaud
approved these changes
Nov 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
UnifiedPush AND_3 spec requires that server-to-server communication use encrypted WebPush requests. Currently the OpenDHT proxy does not do that. Following the advice in this issue https://codeberg.org/UnifiedPush/wishlist/issues/22 this PR worksaround the issue by making the request look like a real encrypted WebPush request following the example the FindMyDevice server is using https://gitlab.com/fmd-foss/fmd-server/-/merge_requests/101
This should be okay as the actual message contents are e2ee (to my knowledge) so if we just mark the payload as encrypted we can make unifiedpush servers happy.