Skip to content
  • Thomas Haller's avatar
    libnm: accept invalid connections in NMVpnServicePlugin · 559ab7bd
    Thomas Haller authored
    When we receive a connection from NetworkManager it is not guaranteed
    that the connection verifies. For example, if the current libnm version
    is older then the NetworkManager version.
    
    Be more accepting and don't do any verification of the connection.
    
    For NMVpnPluginOld this change is uncritical, because there are probably
    no users of this API anyway.
    
    NMVpnServicePlugin is new API since nm-1-1. However, this API is already
    strongly used by all the plugins we ported over. So this change is
    affecting them.
    This should only matter if libnm's and NetworkManager's version differ,
    because NetworkManager just doesn't send out an invalid connection. It
    actually only matters if NetworkManager is a newer version and sends an
    invalid connection to the client. That is anyway badly tested and probably
    this changes rather improves compatibility than breaking existing users.
    559ab7bd