Skip to content
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

Idea for article: Force/suggest upgrade #19

Open
hfossli opened this issue Jun 1, 2018 · 3 comments
Open

Idea for article: Force/suggest upgrade #19

hfossli opened this issue Jun 1, 2018 · 3 comments

Comments

@hfossli
Copy link
Contributor

hfossli commented Jun 1, 2018

I'm just tossing out this idea as I think it might be a good for ios-factor.com.

It should be possible for the server to make the app stop working (or prompt the user with a warning) if there is some serious vulnerability issue with the installed version.

Every API call to the primary backend-server should send the following values

app_version (1.0.0)
app_build_number (f477d3b)
device_model (iPhone1,1)
os_version (10.11)
app_identifier (com.ios-factor.app)
system_language (nb_NO)

Use names of your liking. We pass these values in request headers, but do as you like. The server should then be able to respond with http code 403 or the server may tag a long a warning using for example response headers. The error returned from server should state that the app needs to be upgraded because of a security vulnerability and in what way users are affected. We use the terms suggest upgrade and force upgrade.

@hfossli
Copy link
Contributor Author

hfossli commented Jun 1, 2018

If you like the idea of having such an article on ios-factor I would gladly spend the time writing a proper pull request.

@KrauseFx
Copy link
Member

KrauseFx commented Jun 1, 2018

Hey that's interesting, thanks for the idea. Do you think this is partly covered with #15?

@hfossli
Copy link
Contributor Author

hfossli commented Jun 4, 2018

I don't think #15 clearly conveys the need for warning/forcing users to upgrade their app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants