TROVE-2023-006 vulnerability not yet addressed in Whonix-16?

[Patrick]

I am not doing that to avoid the extraneous maintenance burden.

related:

maintainability

Focus on low-effort maintainability

Quote Tails Focus on low-effort maintainability Many, many Live system projects — including a few ones that aimed at enhancing their users’ privacy — have lived fast and died young. We explain this by their being one wo/man efforts, as well as design decisions that made their maintenance much too costly timewise and energywise. We want Tails to live as long as it is needed: Tails is not meant to be solely a pet project. Since the early days of this project (i.e. early 2009), ease of maintena…

---

Additionally in context of this ticket. For anyone who doesn’t know…

Whonix 16 is “oldstable”, speak outdated. Its support is only dragged along due to Qubes R4.2 still being RC instead of final. Kinda Qubes “LTS” (“long term support”).

I don’t think “LTS” / two major versions at the same time support is a good idea given the already sparsely available resources.

Development focus in on Whonix 17, where all packages are more upgraded and therefore hopefully be more secure.

---

If you care about new / sophisticated attacks being addressed / hosting onion services, I don’t think it’s a good idea to stay on “oldstable” / “LTS”.

Hence my previous answer:

TROVE-2023-006 vulnerability not yet addressed in Whonix-16?

It doesn’t make sense for me to stay on Qubes R4.1 / Whonix 16. related: Qubes-Whonix Support Schedule If you want newer Tor versions quicker, see this: (Whonix is based on Kicksecure.) If Debian doesn’t fix this then this is unlikely to get fixed.