-
-
Notifications
You must be signed in to change notification settings - Fork 386
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
Issues w/ adding Steam profile #390
Comments
I believe Steam shared_secret is base64 encoded (I use it for stidler.com). If that helps. Adding support for Steam would be difficult as the user would have to manually extract their code each time but could be possible |
I recently tried the other method, importing from app (sorry, didn't notice it before!). This returned the error:
UPDATE:Yay! I got it working. I copied the "Steamguard-XXXX" file from the steam android app data directory. Moved it onto the root of the sdcard. Then did "Import from file", selected the file I just moved. To my surprise, this actually successfully worked! The import was successful and the Steam account is now on the list of Aegis! |
As @Committing noted, Steam encodes the secret in base64, while Aegis expects it to be encoded in base32. And as you discovered, Aegis handles this automatically when using the import functionality. The |
No, I only had one in the /data/data/Aegis directly. This was before I even copied the file onto the sdcard. |
Do you mean the |
Closing this issue as this does not seem to be reproducible. |
I used this to translate the key into the format required for Aegis and chose "Steam" as type.
So basically you have to base64 decode your |
This how did it today.
What I did was:
1. Extract tokens from phoneRequires root (or root in a recovery)
2. Add authenticator using python libraryIn an interactive python session: import steam.webauth as wa
import steam.guard as guard
wa = wa.MobileWebAuth("username", "password") # needed?
steam_id = "xxx"
tok = "yyy" # starts with "ey..."
session = wa.oauth_login(tok, steam_id=steam_id)
print("session", session)
sa = guard.SteamAuthenticator(backend=wa)
# sa.remove() # remove currently authenticator if needed
sa.add()
sa.finalize("code from sms") # had to retry this a few times
print(sa.secrets) # backup this securely, contains recovery code and other important things
print(sa.uri.replace("otpauth://totp/", "otpauth://steam/"))
# keep this shell opened to that you can sa.remove() in case things fail 3. Add to aegisIn another shell qrencode -t ansiutf8 <<< 'otpauth://steam/...' Scan the QR code in aegis Cheers, Based on: |
Info
Steps to reproduce
Hi, I am trying to add Steam 2FA onto this Android App Aegis. I noticed Steam in the dropdown menu of the app; & proceeded with submitting a Google Play review, to confirm that its referring to Steam. I followed instructions on how to obtain a "shared_secret". After doing some research, I came to the conclusion that "shared_secret" is the secret needed for the new profile.
I selected the Steam dropdown from the list of types (Right after TOTP & HOTP, the third being Steam). I successfully obtained my shared_secret, & attempted to add the profile. Lastly, I select "save" to finish the profile. From there, I get the error: "Add new profile" it returns: "Secret is not valid base32". I consulted the creator of the github repo that I used to obtain the "shared_secret" from (this case being "Steam Desktop Authenticator"). His response was that shared_secret isn't the field I should be looking for, and that the app needs to add specific support for using one of those. I concluded that the best course of action was to make a GitHub Issue thread, as this seems to be more of an issue with Aegis app itself, rather than Steam.
What do you expect to happen?
I expected the app to successfully add the profile to my Aegis list of 2FA services.
What happens instead?
Returned "Error saving profile": "Secret is not valid base32".
Log
I would add a screenshot, but the app has a secure flag, that prohibits taking screenshots while this app is in the foreground.
The text was updated successfully, but these errors were encountered: