Feature #849
closed
Consider switching Unknown Network to be considered an Antiquated Protocol
Added by Soren Stoutner almost 2 years ago.
Updated almost 2 years ago.
Description
Unknown Network sometimes appears when the signal is too weak for a connection to be made.
Currently, an unknown network registers as a Secure Network (along with 5G NR and IWLAN). The thought process behind this was that an unknown network will not be used to transfer data, therefore it is secure from IMSI catchers intercepting such data. Also, when a network is brought online it sometimes registers an unknown while the protocol is being negotiated. As such, assuming that 5G NR becomes ubiquitous, this minimizes flapping of the notification.
But in the case of a weak signal (like camping in a remote rural area), when the connection is made the protocol is currently more likely to be Antiquated or Insecure. In these scenarios, the current design causes a lot of flapping of notifications.
- Subject changed from Switch Unknown Network to be considered an Antiquated Protocol to Consider switching Unknown Network to be considered an Antiquated Protocol
- Description updated (diff)
As https://redmine.stoutner.com/issues/851 has been implemented, both the Voice and the Data networks are now considered when calculating the overall security. I am going to wait and do some further testing to see if this increases or decreases this flapping problem. With the new design, as long as either the voice or the data network registers as insecure or antiquated, a secure notification will not be fired. So, it might end up with a decrease of flapping as rural connections might consistently register at least one of these at a lower level.
- Status changed from New to Closed
Experience indicates that the current configuration is the correct behavior.
Also available in: Atom
PDF