https://www.whonix.org/wiki/Chat#Tor_Messenger

/usr/lib/apt-get-wrapper:

• https://github.com/Whonix/whonixcheck/blob/12b77823d3df94075f447212bd279e1c578ca65d/usr/lib/apt-get-wrapper
• https://github.com/Whonix/whonixcheck/blob/master/usr/lib/apt-get-wrapper

For the record, slightly off-topic.
Qubes Q3 RC1, Whonix 10.

Too long ago... Trying to find this again...

care to give any details about indefinite freeze and downgrade attacks that gentoo has?

Fixed "vga=ext is deprecated. Use set gfxpayload=text before linux command instead". Upgraded for grub2 / Debian jessie.:
https://github.com/Whonix/grub-screen-resolution/commit/c3b653a27c95f2b513953c63b714962746ae09a3

1. Error when attempting to update in Whonix 10

For the record, flushing all rules and defaulting to ACCEPT makes obfsproxy work.

This seems to have gotten lost in the backlog.

Thanks for all the info. I will test it out over the weekend!

• works for me in Whonix 10
• Documentation: https://www.whonix.org/wiki/Bridges
• obfsproxy: https://www.whonix.org/wiki/Bridges#Using_obfuscated.2C_.28private.29_and.2For_ordinary_bridges
• no different firewall rules required for obfs3
• no startup scripts required
• no other fancy stuff required
• user configuration is simply added to /etc/tor/torrc
• make sure the obfsproxy package is installed
• apparmor was an issue in past, try obfsproxy yourself and check /var/log/kern.log
• for now, just try it out yourself. Does it work for you? If it works for you, if you can confirm from /var/log/tor/log and arm, that Tor is in fact connecting only to the obfs3 bridges you configured, then it's more likely a user configuration error than Whonix bug.

@Patrick I was wondering if this is working in regular Whonix 10? If so can you give me some clues on how to troubleshoot it (startup scripts, configuration locations, expected firewall rules) since I have never used it before

This has been fixed in T274. control-port-filter-python has a working systemd unit file now. Closing. Please re-open if you still see an issue here.

In T273#4175, @Patrick wrote:

What's next here?

@nrgaway Can you please post all your existing systemd units for packages developed under the Whonix umbrella somewhere? Such as the one in the comment of https://phabricator.whonix.org/T273#3852 ? + Add the license header? That would be important. It's currently a blocker before I can continue with most Whonix 11 development tasks. I would like to integrate those into packages and make those systemd-only. I guess I am getting to that before you?

Just finished making whonix-initializer systemd-only. Once the systemd unit is ready, the required remaining changes in debian/control and debian/rules are minimal and simple.

1. HOW TO RE-INSTALL qubes-whonix

Can workstation templates also be upgraded that way? That's not clear from instructions.

In T288#4229, @Patrick wrote:

Your instructions sound good. I recommend to hit the edit button for instruction posts and to copy it over to the wiki https://www.whonix.org/wiki/Qubes/Upgrade_from_9_to_10 or so. Unfortunately, phabricator uses markdown and mediawiki uses mediawiki syntax.

Your instructions sound good. I recommend to hit the edit button for instruction posts and to copy it over to the wiki https://www.whonix.org/wiki/Qubes/Upgrade_from_9_to_10 or so. Unfortunately, phabricator uses markdown and mediawiki uses mediawiki syntax.

1. What to do if you ran a apt-get dist-upgrade not using the upgrade method above

Link: "stable vs wheezy repository" bug T233

In T288#4212, @Patrick wrote:

Yes. Done, migrated (copied) qubes-whonix 10.0.5-1 from developers to testers repository.

Want to post a blog post? Otherwise I guess very few will notice these instructions. Got a blog account already?

Yes. Done, migrated (copied) qubes-whonix 10.0.5-1 from developers to testers repository.

In T288#4179, @Patrick wrote:

I am not sure it's wise telling testers to enable the developers repository. That could break badly at some point. The developers repository is a playground for me to upload and install from packages where I am not 100% certain they are not going to break the package manager.

Related, see also:
https://www.whonix.org/forum/index.php/topic,560.msg7989.html#msg7989

I am not sure it's wise telling testers to enable the developers repository. That could break badly at some point. The developers repository is a playground for me to upload and install from packages where I am not 100% certain they are not going to break the package manager.

What's next here?

1. Testers Update instructions

Thanks, tests are successful for me.

Signed, pushed 10.0.5-1 and added to developers repository.

@Patrick, I created a new version that hopefully solves the control-port-filter-python not re-enabling properly... I had a typo in the maintainers postinst configuration file.

In T275#4134, @nrgaway wrote:

XXX: @Patrick, do your scripts ignore backed up files in directories such as /etc/whonix_firewall.d....

Maybe you want to give an upgrade a try. The required qubes package is now also in the ITL test repo so you should be able to attempt an update. DO NOT FORGET TO BACKUP (CLONE) your existing whonix proxy :)

In T275#4132, @Patrick wrote:

Alright.

How would users upgrade the qubes-whonix package then? Does the ITL repo also contain Debian packages?

How would users upgrade the qubes-whonix package then? Does the ITL repo also contain Debian packages?

In T275#4130, @Patrick wrote:

In T275#4128, @nrgaway wrote:

hehe, I was wondering why it was not in repo. Yes, please add it as I want to do some upgrade testing.

Done, added to developers repository.

In T275#4128, @nrgaway wrote:

hehe, I was wondering why it was not in repo. Yes, please add it as I want to do some upgrade testing.