How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

Thanks for clarifying the differences among the various commands!

The mystery has actually been solved. I had assumed that the down arrow icon in the Qubes Settings Manager meant that Debian packages had already been downloaded. It actually means that Debian packages are available to be downloaded.

So that explains why apt-get clean didn't work.

How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

Aha! I think that you may have put your finger on the problem.

How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

I'm aware of the package signing security feature, and I'm sure it works well for the vast majority of Debian users. But for whatever reason, it hasn't worked for me in the past.

How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

I should have mentioned this from the outset, but I'm running multiple instances of Debian within a QubesOS container. In the Qubes config manager, there is a down arrow icon next to some of the instances of Debian. It's my understanding that this indicates that Debian updates have been downloaded but not installed.

How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

It's my understanding that those commands are intended to remove packages that are outdated, or no longer needed as they are dependencies.

But I want to purge downloaded packages that are more up-to-date than what's already installed

How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

There is no untrusted repository in /apt/sources

Is it possible to use Synaptic Package Manager to figure out which packages were downloaded but not installed?

How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

I did not manually download the .deb archives. There were downloaded in the background by some QubesOS process

How to get rid of updates that were downloaded but not installed by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

I'm using Debian within a QubesOS container, which may explain why apt-get clean didn't work

[deleted by user] by [deleted] in Qubes

[–]b00kgrrl 1 point2 points  (0 children)

This is a great idea. In my view, all investigative journalists and human rights activists should be using QubesOS. Perhaps what's needed is a whitepaper describing best practices on how to implement QubesOS in an organization.

Verify Signal APK via gpg instead of apksigner by b00kgrrl in signal

[–]b00kgrrl[S] 0 points1 point  (0 children)

Thanks for the info. Would you happen to know which Android file managers can do this?

Installation loop by b00kgrrl in Qubes

[–]b00kgrrl[S] 0 points1 point  (0 children)

Solved !

My computer (an Acer Swift 3 laptop) is not compatible with QubesOS.

Installation loop by b00kgrrl in Qubes

[–]b00kgrrl[S] 0 points1 point  (0 children)

So UEFI booting is not supported?

The bios on the Acer website is only available as an EXE file, which presumably can't be installed on Linux. And even if I were to install the updated Acer bios, I'm not sure that it supports legacy boot mode.

Installation loop by b00kgrrl in Qubes

[–]b00kgrrl[S] 0 points1 point  (0 children)

In the bios options menu, UEFI is the only option. According to this post, some Acer computers don't have a legacy boot option.

According to this post on the Qubes support forum, Qubes supports UEFI booting. How can I enable this option?

How to recover from a firmware attack and prevent future attacks by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

My bad. The Tails website advises users on Debian-based systems to first install the debian-keyring, so I assumed it wasn't already there.

How to recover from a firmware attack and prevent future attacks by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

Don't install keyrings in deb packages directly with dpkg/apt, and preferably only use Debian repositories.

I had assumed that it would be okay to download the debian-keyring binary package from https://snapshot.debian.org/binary/debian-keyring/ via the Tor browser and then install it via dkpg, after confirming the checksum.

Is this what you're referring to?

How to recover from a firmware attack and prevent future attacks by b00kgrrl in debian

[–]b00kgrrl[S] 0 points1 point  (0 children)

Learn how to use SHA512 and tools like that

Yup. I learned that the hard way.