Hi Viktor, Version 2.2.11 is not available in the COPR repo. I'm still confused about the current state of packages. 2.2.9 appears to still be the latest version of 389DS for Rocky 8/9, when using the instructions on this page: https://www.port389.org/docs/389ds/download.html Based upon your email, shouldn't that repo offer at least 2.2.11? Thanks in advance for your advice, -Bryan On Thu, Sep 10, 2026 at 01:38:34PM +0200, Viktor Ashirov via 389-users wrote: > Hello, > > The 389 Directory Server team published security updates for multiple > release branches: > > - 3.3.1 (https://www.port389.org/docs/389ds/releases/release-3-3-1.html) > - 3.2.3 (https://www.port389.org/docs/389ds/releases/release-3-2-3.html) > - 3.1.5 (https://www.port389.org/docs/389ds/releases/release-3-1-5.html) > - 3.0.7 (https://www.port389.org/docs/389ds/releases/release-3-0-7.html) > - 2.9.1 (https://www.port389.org/docs/389ds/releases/release-2-9-1.html) > - 2.8.2 (https://www.port389.org/docs/389ds/releases/release-2-8-2.html) > - 2.6.3 (https://www.port389.org/docs/389ds/releases/release-2-6-3.html) > - 2.4.7 (https://www.port389.org/docs/389ds/releases/release-2-4-7.html) > - 2.2.11 (https://www.port389.org/docs/389ds/releases/release-2-2-11.html) > - 1.4.3.41 ( > https://www.port389.org/docs/389ds/releases/release-1-4-3-41.html) > > These releases address multiple security vulnerabilities, including > remotely exploitable issues such as: > - CVE-2026-18922 <https://access.redhat.com/security/cve/CVE-2026-18922> - > 9.8 Critical > - CVE-2026-19843 <https://access.redhat.com/security/cve/CVE-2026-19843> - > 8.4 Important > - CVE-2026-11770 <https://access.redhat.com/security/cve/CVE-2026-11770> - > 7.5 Moderate > - CVE-2026-18355 <https://access.redhat.com/security/cve/CVE-2026-18355> - > 7.5 Important > - CVE-2026-18453 <https://access.redhat.com/security/cve/CVE-2026-18453> - > 7.5 Important > - CVE-2026-76560 <https://access.redhat.com/security/cve/CVE-2026-76560> - > 7.5 Important > - CVE-2026-9064 <https://access.redhat.com/security/cve/CVE-2026-9064> - > 7.5 Important > > Please treat this as a critical security update. Review your installed > version and upgrade to the latest applicable release as soon as possible. > > Regards, > The 389 Directory Server team > -- > _______________________________________________ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org > Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new -- Bryan K. Walton 319-337-3877 Senior Linux Systems Administrator Leepfrog Technologies, Inc -- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Monday, September 14, 2026
[fedora-arm] Re: Latest brcmfmac breaks RPI5 wifi
> It does & did connect to an Android 16 AP/hotspot. > > It also connects to my AP in what it calls compatibility mode, which I think must just be WPA1. No, it's not, it's a transition mode somewhere between WPA2 and WAP3. > After upgrading to your (Peter's): > > Linux nas6 7.2.5-300.pr3.fc45.aarch64 #1 SMP PREEMPT_DYNAMIC Fri Sep 11 20:30:22 UTC 2026 aarch64 GNU/Linux > > I can now connect to LEGGWLAN: There's nothing in there that would affect brcmfmac that's not in the upstream kernels so that mostly just tells me that the issue is environmental. > On an RPI5 with latest F45 stuff, I get this many channels listed: That's not channel, that's SSIDs. > However, on an RPI4 with the latest F45 stuff, I get roughly twice as many. Are they in the same location? In the same case etc? Overall WPA3 isn't currently supported upstream with the old firmware on brcmfamc, the new firmware brings in some changes that will eventually allow WPA3 to work on upstream (ie Fedora and other distos) platforms, but we are not there yet. There's a number of sub standards that are required, or in some case optional, for WPA3 support and like all things that require interoperability different companies have different opinions on what those requirements are. Some of these are firmware related, some a kernel, and some are userspace (NM, wpa_supplicant, possibly other bits) and there's a number of bits still in flux. The SAE (Simultaneous Authentication of Equals) component of of WPA3 which does the auth has a number of options (NnP - Hunt and Peck, H2E - Hash 2 Element). Some APs only enable one or the other of HnP or H2E, similarly some clients also only support one. Digging into this generally it's fragile as hell in brcmfmac (I have tried a number of times over the years to make WPA3 work on brcmfmac) but also generally. I think there's still some work to happen here, the new firmware at least unlocks the vendor side of things. Peter > Thanks for your help. > > :D > > > On 12/09/2026 10:57, Peter Robinson wrote: > > Does it connect to a mobile AP from your phone? > > On Sat, 12 Sept 2026 at 10:48, David Legg <dwlegg@gmail.com> wrote: > > My other RPI5 running latest F43 can see both wifi ranges: > > nmcli device wifi list > IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY > * 3C:58:36:2B:A2:E4 LEGGWLAN Infra 1 195 Mbit/s 87 ▂▄▆█ WPA2 WPA3 > 92:58:36:2B:A2:E7 LEGGGUEST Infra 1 195 Mbit/s 87 ▂▄▆█ -- > 92:58:36:2B:A2:E8 -- Infra 1 195 Mbit/s 85 ▂▄▆█ WPA3 > 92:58:36:2B:A2:E5 EE WiFi Infra 1 195 Mbit/s 85 ▂▄▆█ -- > BE:0F:F3:4B:60:97 DIRECT-97-HP OfficeJet Pro 9730e Infra 6 65 Mbit/s 84 ▂▄▆█ WPA2 > 3C:58:36:2B:A2:E3 LEGGWLAN Infra 36 540 Mbit/s 75 ▂▄▆_ WPA2 WPA3 > 8E:58:36:2B:A2:E7 -- Infra 36 540 Mbit/s 75 ▂▄▆_ WPA3 > 8E:58:36:2B:A2:E4 EE WiFi Infra 36 540 Mbit/s 75 ▂▄▆_ -- > 8E:58:36:2B:A2:E6 LEGGGUEST Infra 36 540 Mbit/s 75 ▂▄▆_ -- > > The top 5 are shown in green, the bottom ones in red. The red ones are the 5Ghz ones aren't they? > > > On 12/09/2026 10:31, Peter Robinson wrote: > > But does it? None of your LEGG show up in the 5ghz range? -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[fedora-arm] Re: Latest brcmfmac breaks RPI5 wifi
It does & did connect to an Android 16 AP/hotspot.
It also connects to my AP in what it calls compatibility mode, which I think must just be WPA1.
Other interesting developments:
After upgrading to your (Peter's):
Linux nas6 7.2.5-300.pr3.fc45.aarch64 #1 SMP PREEMPT_DYNAMIC Fri Sep 11 20:30:22 UTC 2026 aarch64 GNU/Linux
I can now connect to LEGGWLAN:
# nmcli device wifi connect LEGGWLAN
Device 'wlan0' successfully activated with 'c348159a-8ff0-3993-98a9-a7f26a906cad'.
and a phone AP (moto g75 5G_3501) and the EE AP in compatibility mode (LEGGWLANCOMPATIBLE).
On an RPI5 with latest F45 stuff, I get this many channels listed:
# nmcli device wifi list
IN-USE BSSID SSID MODE BAND CHAN RATE SIGNAL BARS SECURITY
06:34:42:1B:59:18 moto g75 5G_3501 Infra 2.4 GHz 11 1170 Mbit/s 100 ▂▄▆█ WPA2 WPA3
BE:0F:F3:4B:60:97 DIRECT-97-HP OfficeJet Pro 9730e Infra 2.4 GHz 6 65 Mbit/s 97 ▂▄▆█ WPA2
92:58:36:2B:A2:E5 EE WiFi Infra 2.4 GHz 1 195 Mbit/s 79 ▂▄▆_ --
92:58:36:2B:A2:E7 LEGGGUEST Infra 2.4 GHz 1 195 Mbit/s 79 ▂▄▆_ --
92:58:36:2B:A2:E9 LEGGWLANCOMPATIBLE Infra 2.4 GHz 1 195 Mbit/s 77 ▂▄▆_ WPA1 WPA2
8E:58:36:2B:A2:E7 -- Infra 5 GHz 36 540 Mbit/s 69 ▂▄▆_ WPA3
EC:FD:F8:22:51:EE AP_2361625852 Infra 2.4 GHz 1 135 Mbit/s 67 ▂▄▆_ WPA2
3C:58:36:2B:A2:E3 LEGGWLAN Infra 5 GHz 36 540 Mbit/s 67 ▂▄▆_ WPA2 WPA3
8E:58:36:2B:A2:E4 EE WiFi Infra 5 GHz 36 540 Mbit/s 67 ▂▄▆_ --
8E:58:36:2B:A2:E6 LEGGGUEST Infra 5 GHz 36 540 Mbit/s 67 ▂▄▆_ --
* 3C:58:36:2B:A2:E4 LEGGWLAN Infra 2.4 GHz 1 195 Mbit/s 66 ▂▄▆_ WPA2 WPA3
58:D6:1F:C8:D3:31 CHEEKYCP Infra 5 GHz 48 1170 Mbit/s 39 ▂▄__ WPA2 WPA3
However, on an RPI4 with the latest F45 stuff, I get roughly twice as many.
Thanks for your help.
:D
Does it connect to a mobile AP from your phone? On Sat, 12 Sept 2026 at 10:48, David Legg <dwlegg@gmail.com> wrote:My other RPI5 running latest F43 can see both wifi ranges: nmcli device wifi list IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY * 3C:58:36:2B:A2:E4 LEGGWLAN Infra 1 195 Mbit/s 87 ▂▄▆█ WPA2 WPA3 92:58:36:2B:A2:E7 LEGGGUEST Infra 1 195 Mbit/s 87 ▂▄▆█ -- 92:58:36:2B:A2:E8 -- Infra 1 195 Mbit/s 85 ▂▄▆█ WPA3 92:58:36:2B:A2:E5 EE WiFi Infra 1 195 Mbit/s 85 ▂▄▆█ -- BE:0F:F3:4B:60:97 DIRECT-97-HP OfficeJet Pro 9730e Infra 6 65 Mbit/s 84 ▂▄▆█ WPA2 3C:58:36:2B:A2:E3 LEGGWLAN Infra 36 540 Mbit/s 75 ▂▄▆_ WPA2 WPA3 8E:58:36:2B:A2:E7 -- Infra 36 540 Mbit/s 75 ▂▄▆_ WPA3 8E:58:36:2B:A2:E4 EE WiFi Infra 36 540 Mbit/s 75 ▂▄▆_ -- 8E:58:36:2B:A2:E6 LEGGGUEST Infra 36 540 Mbit/s 75 ▂▄▆_ -- The top 5 are shown in green, the bottom ones in red. The red ones are the 5Ghz ones aren't they? On 12/09/2026 10:31, Peter Robinson wrote: But does it? None of your LEGG show up in the 5ghz range?
-- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[Test-Announce] Test Days: KDE Plasma 6.7
Please join us for upcoming Test Days and help us improve Fedora's quality and stability.
Your participation helps us find and fix bugs before the next release, ensuring a smoother experience for all users.
This time we'll focus on testing KDE Plasma 6.7.
You'll install Fedora from the provided test image and report your test results along with your hardware configuration.
Test period: 2026-09-14 to 2026-09-20
Test instructions: https://fedoraproject.org/wiki/Test_Day:2026-09-14_KDE_Plasma_6.7
Thank you for your contributions!
Jaroslav Groman
Fedora Quality
-- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Sunday, September 13, 2026
[Test-Announce] 2026-09-14 @ 15:00 UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2026-09-14 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting&iso=20260914T15&p1=1440&ah=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 45 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[Test-Announce] 2026-09-14 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
# F45 Blocker Review meeting # Date: 2026-09-14 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 1 proposed blocker and 4 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20260914T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[fedora-arm] 2026-09-14 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
# F45 Blocker Review meeting # Date: 2026-09-14 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 1 proposed blocker and 4 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20260914T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new