We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2015-09-12 11:52:22 +0200 |
Even when the screen is locked with a pincode the SMS pop up shows the whole message in its usual marquee form..
2 | retagged |
Even when the screen is locked with a pincode the SMS pop up shows the whole message in its usual marquee form..
3 | No.3 Revision |
Even when the screen is locked with a pincode the SMS pop up shows the whole message in its usual marquee form..
4 | No.4 Revision |
Even when the screen is locked with a pincode the SMS pop up shows the whole message in its usual marquee form..
Edit: More detailed description of the issue by @MMx: I am running 1.1.9.28 on the Jolla phone. The phone was locked, and I received a SMS containing a mTAN, and the first line of this SMS was readable in the notification banner which showed up although the phone was locked. If the actual mTAN would have been in the first line, any attacker to my account having my (locked) phone would have been able to make transactions.
Expected result: No notification banner as long as phone is locked, or just minimal "1 new message" or something like that. It should neither contain the sender nor any part of the content.
This should be fixed for final 2.0.
5 | No.5 Revision |
Even when the screen is locked with a pincode the SMS pop up shows the whole message in its usual marquee form..
Edit: More detailed description of the issue by @MMx: I am running 1.1.9.28 on the Jolla phone. The phone was locked, and I received a SMS containing a mTAN, and the first line of this SMS was readable in the notification banner which showed up although the phone was locked. If the actual mTAN would have been in the first line, any attacker to my account having my (locked) phone would have been able to make transactions.
Expected result: No notification banner as long as phone is locked, or just minimal "1 new message" or something like that. It should neither contain the sender nor any part of the content.
This should be fixed for final 2.0.