Package: udisks2
Version: 2.10.1-5
Seen on Chromebook.
Setting up udisks2 (2.10.1-5) ...
vda: Failed to write 'change' to
'/sys/devices/platform/1.pci/pci:00/:00:04.0/virtio3/block/vda/uevent':
Permission denied
vdb: Failed to write 'change' to
'/sys/devices/platform/1.pci/pci0
I think the idea that HFS+ is not used on removable device is a bit of a
fallacy. I, myself, use this frequently on removable hard drives when moving
large data sets back and forth from my Mac. The Mac doesn't easily read ext
filesystems, but Linux can read HFS, and the various Microsoft files
On Jan 10, Michael Biebl wrote:
> While we could ship such a udev rule for udisks, I don't think it will
> properly solve the issue. The device will still show up in nautilus, plasma
> etc and mounting is just an additional click away.
The threat model here is: somebody connects a crafted USB sti
On Sun, 27 Aug 2023 02:34:04 +0200 Marco d'Itri wrote:
So I propose this content for a file like
/usr/lib/udev/rules.d/75-insecure-fs.rules:
While we could ship such a udev rule for udisks, I don't think it will
properly solve the issue. The device will still show up in nautilus,
plasma etc
On Sun, 27 Aug 2023 02:34:04 +0200 Marco d'Itri wrote:
Control: reassign -1 udisks2
Control: retitle -1 do not mount automatically unmaintained file systems
On Jul 20, md wrote:
> You are totally correct.
> Kernel team, please blacklist HFS/HFS+ for automounting.
As discussed on debian-devel@,
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 10 Jan 2024 12:28:58 +0100
Source: udisks2
Architecture: source
Version: 2.10.1-5
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
Changed-By:
udisks2_2.10.1-5_source.changes uploaded successfully to localhost
along with the files:
udisks2_2.10.1-5.dsc
udisks2_2.10.1-5.debian.tar.xz
udisks2_2.10.1-5_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing commands for cont...@bugs.debian.org:
> fixed 1057767 1.0.0-3
Bug #1057767 [src:pipewire] pipewire: Last upgrade completely broke bluetooth
connection: : org.bluez.Error.Failed br-connection-unknown
Marked as fixed in versions pipewire/1.0.0-3.
>
End of message, stopping processing her
