2 Discussions started
8 Comments posted
11 Points earned
1 Solutions given
- Last Active
I don't think there is a possibility for injection even though it looks like the '#' character ends up (non-url encoded?) in the portal URL. On desktop and when accessing My FS Protection later the URL is anyway user modifiable in the browser addres…
So F-Secure found the root cause: if there is a '#' in the device name, loading the login screen will fail. My son's device name was '##lol##' Renaming the device in device settings fixed the problem.
@nanonyme wrote: Sounds suspicious. Have you reported a bug on beta.f-secure.com already? Yeah, I have reported this.
This happens consistently on my sons phone. And since I reinstalled FS Protection, the phone is now without protection (because cannot perform the initial login to My FS Protection in order to set up protection).
Both phones have similar configuration. Also, the login screen is embedded inside FS Protection app so the browser should not affect it in any way.
Looks like the upgrade fixed the problem \o/ Case closed.
Noticed the upgrade, I updated last evening. So far so good, no crashes since that. Fingers crossed :)
I'm using my phone as the main user, application/parental controls are not in use. My wife is experiencing same problem, she has similar phone as I do and also using FS Protection as the main user.