mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
qbittorrent-5.0.5_lt20.dmg is "damaged" due to apple quarantine requirement #17178
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17178
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Artoria2e5 on GitHub (Sep 16, 2025).
qBittorrent & operating system versions
qBitTorrent 5.0.5
Darwin Kernel Version 24.6.0
macOS Sequoia 15.6
What is the problem?
System complains that dmg file is damaged and refuses to mount. This can be circumvented via
xattr -d com.apple.quarantineon the file. I guess it wants downloaded (quarantined) files to be signed somehow and this file isn;t.Steps to reproduce
Additional context
Log(s) & preferences file(s)
This is really irrelevant because this happens before one can run the app.
@ghost commented on GitHub (Sep 25, 2025):
on 26 I find I have to try and mount the image, be refused, then go into settings->security and there will be a message there about the failed mount, verify it's ok there and retry. Process was a bit different on prior OS versions.
I've found the same for other unsigned packages as well.
@Vaida12345 commented on GitHub (Oct 10, 2025):
Just a reminder to checksum before mounting it. Can't be too sure about downloaded files.
@garglebutt commented on GitHub (Nov 6, 2025):
Expected behaviour. I'd propose to close.
@Artoria2e5 commented on GitHub (Nov 6, 2025):
Expected by whom? You average user, or your average uber-poweruser who torrents?
I agree that for now we can add a notice to the user about what to do. That said, is checksumming even needed? We do have a code signature on the whole app, which implies automatic checksumming against a known-correct (because it's signed) checksum the moment you open the app for the first time. There's something profoundly silly about all the layers of signing apple wants...
@garglebutt commented on GitHub (Nov 6, 2025):
By anyone who chooses to download and install unsigned packages on MacOS. This is isn't particularly new any more.
@Artoria2e5 commented on GitHub (Nov 6, 2025):
The app inside is signed. Signing the disk image provides no useful extra protection, only from say filesystem driver bugs that occur on mount (well, why is everyone using a disk image? why can't you make tarballs and zips work for the same job, Apple?) and from… perhaps Finder bugs that come with reading the .DS_Store for fancy layout.