-
Notifications
You must be signed in to change notification settings - Fork 24
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
Where to get the "activation code" ? #13
Comments
I have the same exact problem, have you solved it? |
No, never solved it, in the meantime I left the company |
This bug isn't "solveable" without implementing a whole bunch of new workflows, as mentioned Base64/ |
If you figure out how to disable root checks and pinning on this app I could dump the enrollment process for you |
Four years have passed, and I see nobody solved this issue yet. |
Also interested in this. It would appear that there are many MobilePass+ apps available now, macOS and other desk apps included. It definitely still uses HMAC-SHA256 OTP to generate the 8 digit code but I cannot figure out how or where the client gets the OTP secret from. |
Hi
Where would I get the activation code from ?
I more or less has the same problem as this guy in the comments: https://crypto.stackexchange.com/a/13189
All I have from my company is an email with a link to a download page for the MobilePass application and it shows a base64 string which decodes to this:
key matches this regexp: ^[a-zA-Z0-9]{10}$
pin matches this regexp: ^[0-9]{4}$
The text was updated successfully, but these errors were encountered: