~connman-maintainers/connman/head : changes

~connman-maintainers/connman/head » Changes from revision 8681

From Revision 8273 to 8254

Rev	Summary	Authors	Date
8273	build: Use AC_PROG_CC instead of AC_PROG_CC_C99 build: Use AC_PROG_CC instead of AC_PROG_CC_C99	Marcel Holtmann	1 year ago
8272	build: Update to support Autoconf >= 2.69 build: Update to support Autoconf >= 2.69	Marcel Holtmann	1 year ago
8271	build: Use LT_INIT instead of AC_PROG_LIBTOOL build: Use LT_INIT instead of AC_PROG_LIBTOOL	Marcel Holtmann	1 year ago
8270	build: Use AS_HELP_STRING instead of AC_HELP_STRING build: Use AS_HELP_STRING instead of AC_HELP_STRING	Marcel Holtmann	1 year ago
8269	Release 1.42 Release 1.42	Marcel Holtmann	1 year ago
8268	AUTHORS: Mention Oskar's contributions AUTHORS: Mention Oskar's contributions	Daniel Wagner	1 year ago
8267	timeserver: Purge timeserver list after reset timeserver: Purge timeserver list after reset When reset, the timeserver list needs to be purged from whole timesever history, in order to only contain the up-to-date values.	Emmanuel VAUTRIN	1 year ago
8266	rtnl: Ignore adding/removing interface to/from bridge rtnl: Ignore adding/removing interface to/from bridge Avoids wifi interface being removed and added again when tethering is disabled.	Jonathan Liu	1 year ago
8265	ntp: Fix timeserver typo in warning when ntp_data is not NUL... ntp: Fix timeserver typo in warning when ntp_data is not NULL The value of the timeserver variable is incorrectly referred to as timerserver. Change it to timeserver to be consistent.	Jonathan Liu	1 year ago
8264	AUTHORS: Mention Eivind's contributions AUTHORS: Mention Eivind's contributions	Daniel Wagner	1 year ago
8263	vpn: Adding support for latest pppd 2.5.0 release vpn: Adding support for latest pppd 2.5.0 release The API has gone through a significant overhaul, and this change fixes any compile issues. 1) Fixes to configure.ac itself 2) Cleanup in pppd plugin itself Adding a libppp-compat.h file to mask for any differences in the version.	Eivind Næss	1 year ago
8262	service: Fix hidden service with wrong passphrase service: Fix hidden service with wrong passphrase Two cases need to be fixed during the connection to a hidden service with a wrong passphrase: * the invalid key error shall be reported to the user, * another attempt to connect to this hidden service shall be possible, and succeed with the right passphrase	Emmanuel VAUTRIN	1 year ago
8261	network: Keep failure state after disconnection network: Keep failure state after disconnection set_disconnected() function shall not prevent the service to process errors by replacing failure state by idle. For example, when a connection fails with a wrong passphrase, the user still needs to be informed, via the agent. However, in this case, the associated service is automatically disconnected, canceling the pending agent requests. The invalid key error shall be reported, instead of a cancel error.	Emmanuel VAUTRIN	1 year ago
8260	doc: Update connman(8) manpage on the --nodnsproxy option. doc: Update connman(8) manpage on the --nodnsproxy option. The --nodnsproxy option documentation left out that ConnMan will fall back to creating a resolv.conf on startup. This gets fixed by this.	Oskar Roesler	1 year ago
8259	doc: Add info on matching logic for --nodevice doc: Add info on matching logic for --nodevice	Daniel Wagner	1 year ago
8258	AUTHORS: Mention Polina's contributions AUTHORS: Mention Polina's contributions	Daniel Wagner	1 year ago
8257	gdhcp: Verify and sanitize packet length first gdhcp: Verify and sanitize packet length first Avoid overwriting the read packet length after the initial test. Thus move all the length checks which depends on the total length first and do not use the total lenght from the IP packet afterwards. Fixes CVE-2023-28488 Reported by Polina Smirnova <moe.hwr@gmail.com>	Daniel Wagner	1 year ago
8256	service: Fix an additional case of autoconnect breakage unde... service: Fix an additional case of autoconnect breakage under iwd Error flow: - __connman_service_create_from_network() creates network, but it is not favorite since it is not yet saved - trigger_autoconnect is skipped since !favorite * User calls Connect() * - iwd plugin gets connect() call - iwd plugin finds out about new known network and copies the autoconnect state of the iwd_network to the iwd_known_network, which is false since it was zero initialized and nobody called connman_network_set_autoconnect on it. - iwd plugin tells iwd to set AutoConnect to false - service_indicate_state() calls __connman_service_set_favorite(service, true) - nobody tells the iwd plugin about the change in favorite state This patch calls trigger_autoconnect right at the end there, which will then propagate the outcome of the favorite state to the iwd plugin. I think this patch is the right design for the current architecture of the autoconnect state management, but I think the autoconnect design probably needs some changes outside the scope of this patch since it is too easy to make these mistakes.	Jade Lovelace	2 years ago
8255	iwd: fix iwd autoconnect being set wrongly on new connection... iwd: fix iwd autoconnect being set wrongly on new connections Due to an extremely subtle bug in tracking the autoconnect state from connman on through to iwd, iwd was incorrectly being sent zero-initialized default data as the autoconnect value. In particular, what happened is as follows: - A new iwd_network is created for the iwd.Network that appears, which also creates an associated connman_network. In the process of creating the connman_network, the iwd plugin receives a callback that correctly sets the cm_autoconnect state of the iwd_network. - Connman's Service.Connect() function is called via D-Bus, which calls into the iwd plugin, which in turn calls iwd.Network.Connect() over D-Bus. - The connection completes and the following fire: - iwd.KnownNetwork created event, which is supposed to initialize the cm_autoconnect state to that of the iwd_network, but this does not occur since the iwd_network does not yet have a KnownNetwork associated, so it remains uninitialized - PropertyChanged event on the corresponding iwd.Network object, with the new KnownNetwork property value, springing the trap set earlier by synchronizing the zero-initialized iwd_known_network.cm_autoconnect state to the iwd KnownNetwork In practice, this looks like: -> net.connman.iwd.Network.Connect() on /net/connman/iwd/0/3/0000000000000000000000_psk <- RequestPassphrase() -> (passphrase) -> Set('AutoConnect', False) on /net/connman/iwd/0000000000000000000000_psk This was found by investigating why my computer was not automatically connecting to some networks after coming out of sleep, and finding that the iwd AutoConnect setting was false on those networks while connman thought it was true (in fact, this was the case! The connman iwd plugin thought otherwise). Reproduction: connmanctl> agent on Agent registered connmanctl> config wifi_9cb6d0f7daaf_00000000_managed_psk --remove connmanctl> connect wifi_9cb6d0f7daaf_00000000_managed_psk Agent RequestInput wifi_9cb6d0f7daaf_00000000_managed_psk Passphrase = [ Type=psk, Requirement=mandatory ] Passphrase? 00000000 Connected wifi_9cb6d0f7daaf_00000000_managed_psk $ busctl get-property net.connman.iwd /net/connman/iwd/00000000_psk net.connman.iwd.KnownNetwork AutoConnect b false Then sleep the machine and observe that the network is not automatically reconnected.	Jade Lovelace	2 years ago
8254	iwd: Fix typo in create_known_network name iwd: Fix typo in create_known_network name	Jade Lovelace	2 years ago