Repository navigation
Signal history import: Molly's new-format backup read with the recovery key and imported like Discord's - #21
Merged
Merged
Conversation
…ry key and imported like Discord's The recovery key gives the backup key (the only thing the hub keeps), which opens a snapshot's metadata and main; frames map onto the live adapter's own ids and wording (group ids from master keys via zkgroup's Sho), and attachments are unsealed from the shared files folder into the media store. Key steps are pinned against libsignal-client's output and group ids were checked against a real signal-cli account. The History section asks for the recovery key when a folder holds snapshots, counts the newest one, and the import runs through the same dry run / import / undo path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The recovery key gives the backup key (the only thing the hub keeps), which opens a snapshot's metadata and main;
frames map onto the live adapter's own ids and wording (group ids from master keys via zkgroup's Sho), and
attachments are unsealed from the shared files folder into the media store. Key steps are pinned against
libsignal-client's output and group ids were checked against a real signal-cli account. The History section asks
for the recovery key when a folder holds snapshots, counts the newest one, and the import runs through the same
dry run / import / undo path.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com