OLD: Fedora-Rawhide-20230721.n.0
NEW: Fedora-Rawhide-20230722.n.1
= SUMMARY =
Added images:0
Dropped images: 2
Added packages: 4
Dropped packages:2
Upgraded packages: 174
Downgraded packages: 0
Size of added packages: 120.49 KiB
Size of dropped packages
The following Fedora EPEL 9 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eaff7ffae1
kitty-0.26.5-6.el9
The following builds have been pushed to Fedora EPEL 9 updates-testing
netdata-1.41.0-1.el9
partclone-0.3.24-1.el9
The following Fedora EPEL 8 Security updates need testing:
Age URL
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-226639904e
netcdf-4.7.0-3.el8
The following builds have been pushed to Fedora EPEL 8 updates-testing
netdata-1.41.0-1.el8
partclone-0.3.24-1.el8
The following Fedora EPEL 7 Security updates need testing:
Age URL
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-62c97d6572
zabbix50-5.0.36-1.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
netdata-1.41.0-1.el7
partclone-0.3.24-1.el7
Announcing the creation of a new nightly release validation test event
for Fedora 39 Rawhide 20230722.n.1. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On Sat, Jul 22, 2023 at 10:32:01AM +0200, drago01 wrote:
> Which file systems are considered uncommon in that context? And aren't most
> attacks based on file systems used by windows, which makes them "common" ?
> (Extfat, NTFS, VFAT)
Any attack here is going to be OS-specific - a vulnerability
On Sat, Jul 22, 2023 at 3:32 PM Dan Čermák
wrote:
>
> Hi,
>
> Aoife Moloney writes:
>
> > https://fedoraproject.org/wiki/Changes/EnableFwupdRefreshByDefault
> >
> *snip*
> >
> > == Detailed Description ==
> >
> > Firmware for hardware devices can have bugs and firmware updates
> > generally help
On 7/22/23 08:57, Michael Catanzaro wrote:
> I've been thinking about this for a while. The status quo is really
> awful.
>
> On Sat, Jul 22 2023 at 11:31:22 AM +, Zbigniew Jędrzejewski-Szmek
> wrote:
>> A bigger problem I see, is that if a user plugins in a usb stick,
>> expecting to make
On Fri, Jul 21, 2023 at 01:59:47AM +0200, Peter Boy wrote:
> Is there something wrong with the Java-Devel list?
>
> I can send a message to the list and get no reject or error, but is never
> shows up, at least it looks like that.
>
> Or did I miss something?
If you are subscribed it should
On Fri, Jul 21, 2023 at 04:31:01PM +0100, Aoife Moloney wrote:
> https://fedoraproject.org/wiki/Changes/LibreOffice_7.6
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will
On Sat, Jul 22, 2023 at 10:12:33AM -0400, Neal Gompa wrote:
> Several years ago, SUSE distributions moved to disabling the modules
> by default for a number of filesystems, but making it pretty easy to
> turn them back on:
> https://github.com/openSUSE/suse-module-tools/pull/5
The problem there
Hi,
Aoife Moloney writes:
> https://fedoraproject.org/wiki/Changes/EnableFwupdRefreshByDefault
>
*snip*
>
> == Detailed Description ==
>
> Firmware for hardware devices can have bugs and firmware updates
> generally help address those. Firmware updates might however need
> manual interaction, a
On Sat, Jul 22, 2023 09:35:26 -0700, Kevin Fenzi wrote:
> On Sat, Jul 22, 2023 at 11:04:19AM +0100, Ankur Sinha wrote:
>
> > The wiki page also looks out of date (still refers f38):
> > https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
> >
> > I had the usual question---should I be making
On Sat, Jul 22, 2023 at 11:04:19AM +0100, Ankur Sinha wrote:
> On Wed, Jul 19, 2023 13:31:57 +0200, Tomas Hrcka wrote:
> > Oh, that thing again.
> > Let me update the template so sed works correctly.
> >
>
> The wiki page also looks out of date (still refers f38):
>
On Sat, Jul 22, 2023 at 9:53 AM Florian Weimer wrote:
>
> * Matthew Garrett:
>
> > a) Does this seem like a good idea?
> > b) If so, is dealing with it via udev rules the right approach? This way
> > seems desktop-agnostic
> > c) Where should it ship, and what should the process be for disabling
* Matthew Garrett:
> a) Does this seem like a good idea?
> b) If so, is dealing with it via udev rules the right approach? This way
> seems desktop-agnostic
> c) Where should it ship, and what should the process be for disabling it
> for people who need this functionality?
Maybe a first step
I've been thinking about this for a while. The status quo is really
awful.
On Sat, Jul 22 2023 at 11:31:22 AM +, Zbigniew Jędrzejewski-Szmek
wrote:
A bigger problem I see, is that if a user plugins in a usb stick,
expecting to make use of it, and it's not automounted without any
On Sat, Jul 22 2023 at 02:44:30 AM +, "Smith, Stewart via devel"
wrote:
I’d almost prefer we work out a policy where anything of the sort
is disabled by default, and with a distro-wide standard bcond to not
even compile it in as an option. (No, I don’t quite know how that
could be worded
On Sat, Jul 22, 2023 at 07:01:34AM +0100, Matthew Garrett wrote:
> A discussion within Debian again brought up the problem that:
>
> 1) Automounting of removable media exposes the kernel to a lot of
> untrusted input
> 2) Kernel upstream are not terribly concerned with ensuring that kernel
>
On Sat, Jul 22, 2023 at 07:01:34AM +0100, Matthew Garrett wrote:
> A discussion within Debian again brought up the problem that:
>
> 1) Automounting of removable media exposes the kernel to a lot of
> untrusted input
> 2) Kernel upstream are not terribly concerned with ensuring that kernel
>
On Sat, Jul 22, 2023 at 09:08:37AM +0200, Miroslav Suchý wrote:
> Dne 21. 07. 23 v 10:50 Zbigniew Jędrzejewski-Szmek napsal(a):
> > > Is this expected? Or is this sign of something malicious happenening?
> > Dunno. Generally the most likely explanation would be that you have local
> > commits. But
On Wed, Jul 19, 2023 13:31:57 +0200, Tomas Hrcka wrote:
> Oh, that thing again.
> Let me update the template so sed works correctly.
>
The wiki page also looks out of date (still refers f38):
https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
I had the usual question---should I be making new
On Saturday, July 22, 2023, Matthew Garrett wrote:
> A discussion within Debian again brought up the problem that:
>
> 1) Automounting of removable media exposes the kernel to a lot of
> untrusted input
> 2) Kernel upstream are not terribly concerned with ensuring that kernel
> filesystems are
Dne 21. 07. 23 v 10:50 Zbigniew Jędrzejewski-Szmek napsal(a):
Is this expected? Or is this sign of something malicious happenening?
Dunno. Generally the most likely explanation would be that you have local
commits. But if that is impossible, then something strange is going on.
Can you identify
A discussion within Debian again brought up the problem that:
1) Automounting of removable media exposes the kernel to a lot of
untrusted input
2) Kernel upstream are not terribly concerned with ensuring that kernel
filesystems are resilient against deliberately malformed filesystems so
are
25 matches
Mail list logo
