[docs] Update Authy import docs to mention Authy-iOS-MiTM #5445
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
|
|
ua741
changed the title
ua741
approved these changes
Apr 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
This pull request adds mention of the Authy-iOS-MiTM method to Ente's documentation on migrating from Authy. Currently, the only working method to import Authy tokens into Ente is to use a rooted Android device, which is not ideal due to most people not having rooted Android devices. The Authy-iOS-MiTM method (that I made) only requires an iOS device with Authy and a computer with Python and mitmproxy, making it significantly more accessible to people looking to migrate their Authy tokens. By mentioning my method in Ente's Authy import docs, it would help more people discover it and would hopefully make some people's lives easier since they wouldn't have to manually re-register 2FA on every website. Let me know if you have any questions.
Tests
N/A, this pull request does not modify any code