19:02:51 <wilcal> #startmeeting
19:02:51 <Inigo_Montoya> Meeting started Thu Sep 16 19:02:51 2021 UTC.  The chair is wilcal. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:51 <Inigo_Montoya> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:03:02 <wilcal> Welcome to this weeks QA meeting
19:03:16 <wilcal> #topic Who's new?
19:03:30 <wilcal> Anyone new here this week
19:04:15 <wilcal> Nope
19:04:18 <wilcal> #topic Driver Realtek rtl8192eu, do we have a problem here?
19:04:27 <wilcal> Is this an issue?
19:04:48 <bri_an> I had a similar USB device with the same issue.  So yes
19:04:51 <Guygoye[m]> Yes, It was already a problem in MGA8 Cauldron
19:04:51 <wilcal> Seems to be this weeks ML issue
19:05:08 <bri_an> mine stopped working with mga7
19:05:11 <wilcal> Bug assigned to it?
19:05:38 <Guygoye[m]> Not yet
19:05:48 <Guygoye[m]> I don't written it
19:05:58 <wilcal> Age of hardware that needs this fixed?
19:05:58 <MageiaTJ> I'm not sure why we can't make the dkms driver blacklist the rtl8xxxu driver for the user. That's the issue.
19:06:20 <marja> https://bugs.mageia.org/show_bug.cgi?id=28404
19:06:22 <[mbot> 28404 – Wrong driver selected for D-Link N300 Nano USB adapter
19:06:24 <Guygoye[m]> I wanted to do it tonight
19:07:12 <MageiaTJ> The kernel won't load the dkms driver module unless the open source driver is blacklisted.
19:07:40 <Guygoye[m]> I have to put it in /etc/module
19:07:52 <wilcal> Outside our control?
19:08:08 <marja> Guygoye[m]: the bug report already exists, see the link I gave
19:08:25 <Guygoye[m]> Yes i saw it
19:08:55 <Guygoye[m]> Do I have to complete it ?
19:09:19 <marja> and related is https://bugs.mageia.org/show_bug.cgi?id=28795 .. I don't think that became an update
19:09:21 <Luigi12> the dkms package could install a file in /etc/modprobe.d/ that blacklists it...I guess you'd have to see if pterjan or tmb thought that was appropriate
19:09:21 <[mbot> 28795 – Newer rtl8192eu driver with support for kernel 5.12 series
19:10:45 <marja> Guygoye[m]: you can add a comment that it affects you, too
19:11:18 <wilcal> Is there still new hardware being sold that needs this fix?
19:11:42 <MageiaTJ> Yes. Lots of it on Amazon.
19:11:44 <Guygoye[m]> marja: Ok i'll do that
19:11:58 <wilcal> So this is an important fix
19:12:46 <Guygoye[m]> Yes I confirm it is sold under different brands
19:13:13 <Guygoye[m]> I have two dongle with different brand at home
19:13:38 <MageiaTJ> It's an inexpensive usb wifi dongle.
19:13:58 <wilcal> China stuff. one circuit, sold onder 35 brands
19:15:14 <wilcal> Remember about 15 years ago when there was like 230 different kinds of webcams?
19:15:41 <wilcal> Each required a different windows driver
19:15:50 <wilcal> insanity
19:16:26 <wilcal> ANyway this sounds like it's properly documented and being worked on
19:17:43 <Guygoye[m]> Driver that I have on my computer:
19:17:43 <Guygoye[m]> dkms-rtl8192eu-4.4.1-1.20201219.1.mga8
19:19:29 <wilcal> Ok I've got an issue that probably has nothing to do with us
19:19:52 <wilcal> #topic Does the Apple security hack effect us?
19:20:01 <marja> since May, there is dkms-rtl8192eu-4.4.1-1.20210403.1.mga8 in updates_testing
19:20:11 <Luigi12> it doesn't, but there are even more zero-days being exploited in the wild in Chrome
19:20:11 <wilcal> This was a particularly insidious hack. Malware built into a gif that was automatically loaded
19:20:25 <Luigi12> our Chromium package hasn't been updated in *ages* and has several issues being actively exploited at this point
19:20:28 <wilcal> probably has nothing to do with us
19:20:29 <marja> o, the bug report was never assigned to QA
19:20:41 <Luigi12> I suggested that we retire the package and make a blog post
19:20:56 <wilcal> Thanks Luigi
19:21:09 <Luigi12> malware being loaded into a gif isn't a new idea though, and can sometimes affect us
19:21:22 <wilcal> Apple went nuts
19:21:28 <bri_an> Chromium is kind of important I would suggest.
19:21:34 <Luigi12> browser and image decoding library CVEs have exposed those kind of issues in the past, and people have injected malicious images into ad networks before
19:21:55 <bri_an> I mean we can go out and manually install Chrome, but that can be interesting.
19:22:04 <Luigi12> yeah that works pretty well
19:22:16 <wilcal> Would it only effect Chrome?
19:22:30 <Luigi12> we're talking about two different things here, LOL
19:22:33 <wilcal> Firefox is  immune
19:22:46 <Luigi12> so Chrome has had many serious issues, which affect our Chromium package because it hasn't been updated
19:22:49 <Luigi12> yeah Firefox is fine
19:23:05 <Luigi12> but as far as other image library issues, those can hypothetically affect any browser, but that's a separate issue
19:23:12 <wilcal> This was a really severe issue for Apple and a bit of an embarrasment
19:23:28 <Luigi12> yeah Windows had some serious issues very recently too
19:23:35 <Luigi12> it's rough out there
19:23:42 <Luigi12> kind of feels like we're next :o)
19:24:28 <bri_an> Luigi12 I suspect Linux is in lay
19:24:30 <bri_an> play
19:24:42 <wilcal> I would ask, plead, that when the kernel updates come along we post that to the ML. As sometimes they have to be procesed asap
19:25:33 <wilcal> take a breath and give it a few days for everyone to get a shot at testing it
19:26:11 <wilcal> We've not seen any kernel panic errors in years
19:26:37 <Luigi12> yeah tmb at least does post to the ml when it's known to be critical
19:27:40 <wilcal> Anything on the long list that needs discussion?
19:27:56 <Luigi12> ghostscript CVE is apparently pretty severe
19:29:42 <wilcal> I don't even know how to use Postscript :-(
19:30:11 <tarazed> It is like Forth - not easy
19:30:22 <wilcal> Anything else on the list needs discussion?
19:30:45 <bri_an> nothing here
19:31:00 <Guygoye[m]> nothing to me
19:31:06 <wilcal> Then lts move on
19:31:07 <marja> nor for me
19:31:08 <wilcal> #topic Anything else?
19:31:45 <wilcal> The heat in Las Vegas has finaly broken. Only in the 90's here today. But it's a dry heat.
19:32:25 <wilcal> OK Countdown time
19:32:38 <wilcal> thanks all for being here. See you again next week
19:32:42 <wilcal> T-5
19:32:49 <wilcal> T-4
19:32:55 <wilcal> T-3
19:33:01 <wilcal> T-2
19:33:06 <wilcal> T-1
19:33:08 <wilcal> #endmeeting