Use correct VM name for mimetype handling #707
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
Ready for review
Description of Changes
Intended to address #705.
We've observed inconsistent symlinking based on "grains.id", which resolve to the VM hostname in all cases. Let's instead call out to
qubesdb-read /name
, which sidesteps all Salt machinery, and polls for the VM name via the configuration API.Testing
ln -sf /opt/sdw/mimeapps.list.sd-default ~/.local/share/applications/mimeapps.list
insidesd-viewer
to break it. You should confirm inside SecureDrop Client that DispVMs fail to open submissions.make clone
to fetch these changes into dom0sudo dnf reinstall <rpm>
sdw-admin --apply
to do a full state run.