From: Daniel Wagner <wagi@monom.org>
To: connman@lists.linux.dev
Subject: [ANNOUNCE] ConnMan release v1.40
Date: Thu, 10 Jun 2021 13:35:03 +0200 [thread overview]
Message-ID: <20210610113503.ob45lhssqy5hk4ki@beryllium.lan> (raw)
Hi,
We have a new ConnMan release v1.40. It's bug fix release with a fix for
a buffer overflow in dnsproxy (CVE-2021-33833).
Noteworthy are the improvements for iwd. It fixes the autoconnect
interaction between ConnMan and iwd. ConnMan relies completely on iwd to
handle the autoconnect for WiFi.
The OpenConnect VPN plugin got a rewrite and uses libopenconnect for
authentication. This avoids the output screen scrapping done previously.
Thanks everyone who contributed directly or indirectly for their
support.
As you might have noticed ConnMan's mailing list has moved. The project
is now longer hosted on the 01.org infrastructure. This will not change
anything [1]. The last few years I was the only active
maintainer/developer doing it in my spare time so everything will stay
the same (including my very slow responses, sorry).
Thanks,
Daniel
[1] BTW, I've never bothered to collect the old mails. Though with lore
as mail archive I'd like to restore it.If anyone has a complete (or
nearly) complete archive, please share it with me.
Alyssa Ross (1):
README: fix typo
Daniel Wagner (17):
service: Fix integer type for online check interval
mailmap: Update non-canonical log entries
ethernet: Copy interfance names obeying lengths rules
wireguard: Copy interfance names obeying lengths rules
service: Remove unused __connman_service_disconnect_all()
service: Factor auto connect trigger code into a new function
iwd: Init AutoConnect of know networks
iwd: Filter out connect failure for auto connect mode
network: Add __connman_network_native_autoconnect()
service: Teach autoconnect algorithm native mode
wifi: Open code g_memdup
peer: Open code g_memdup
service: Disable native autoconnect calls for providers
timerserver: Fix time update manual->auto
README: Update mailing list info
AUTHORS: Mention Valery's contributions
AUTHORS: Mention Alyssa's contributions
Emmanuel VAUTRIN (9):
wifi: Check valid network in disconnect callback
wifi: Reset disconnecting status of any network
service: Add online check interval config options
service: Add online to ready transition feature
service: Complete only after user connection retries
service: Fix disconnection search before connecting
service: Allow only user connection after WiFi failure
wispr: Support of common redirection status codes
main: Cleanup of vendor class id and wifi config options
Jonathan Liu (1):
iwd: Fix typo in error message when stopping AccessPoint mode
Jussi Laakkonen (5):
dnsproxy: Enable DNS servers on connected VPN if split routing changes
vpn: Return transport ident with get_property()
provider: Add function to get transport ident from VPN
service: Sort VPNs using the transport service if connected
ipconfig: Refactor /proc value get/set to separate functions
Justin Maggard (1):
timeserver: Fix false error message
Marcel Holtmann (2):
README: Remove the 01.org website and the 01.org Jira
Release 1.40
Santtu Lakkala (1):
Rewrite openconnect plugin to use libopenconnect
Valery Kashcheev (1):
dnsproxy: Check the length of buffers before memcpy
reply other threads:[~2021-06-10 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210610113503.ob45lhssqy5hk4ki@beryllium.lan \
--to=wagi@monom.org \
--cc=connman@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).