sdwdate-gui for Qubes. Testers wanted (developers welcome)

Development
7

Merged your pull request.

Updated qubes-core-admin-addon-whonix

Added policies in qubes-core-admin. without the .policy extension.

I do not see what I can do in GitHub - QubesOS/qubes-core-agent-linux: Qubes component: core-agent-linux

Or do we need a new qvm-features-request somewhere ?

1 Like
8

add "anon-gateway" tag · troubadoour/qubes-core-admin-addon-whonix@4bcaa19 · GitHub - this seems wrong, since all of this happens after if 'whonix-ws' in template.features:.

add policies for sdwdate-gui-qubes · troubadoour/qubes-core-admin@a55b8ae · GitHub - this looks good. Could you please also add sys-whonix verbatim? Reason: I guess many people will miss the anon-gateway tag. The problem is, we will invent it after qubes-core-admin-addon-whonix was run for the first time. Or will we delay Whonix 14 until there is a new qubes-core-admin-addon-whonix? By adding sys-whonix verbatim we avoid issues of refused qrexec connections for most users who just use a single sys-whonix. This needs to be explained in the pull request.

I guess we have to invent qvm-features-request whonix-gw=1.

9

I hope not.

Moved anon-gateway tag before the if whonix-ws block.

Added sys-whonix in policies.

1 Like
10

Add "anon-gateway" tag, for Whonix-15. · troubadoour/qubes-core-admin-addon-whonix@5111da0 · GitHub - that would result adding the anon-gateway tag to to workstations as well. It needs some if 'whonix-gw' in template.features: above if 'whonix-ws' in template.features: or so.

Policies for sdwdate-gui-qubes. · troubadoour/qubes-core-admin@daca453 · GitHub - looks good. Created a pull request for it.

11
12

swdate-gui-qubes depends on tor-control-panel

https://github.com/troubadoour/sdwdate-gui/commit/a7408345f1a6f89f29363694533036f06a260c5e

1 Like
13

https://github.com/QubesOS/qubes-core-admin-addon-whonix/pull/2

14

Was merged! :slight_smile:

15

sdwdate-gui[qubes] in VirtualBox.

Ref: http://forums.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/t/kdesudo-error-popup-window-sdwdate-gui/5642/22?u=troubadour

This is whonix-firewall not coming up. sdwdate-gui creates /usr/lib/qubes/notify-shutdown

In whonix-gateway-firewall line 135, we have:

   if [ -d "/usr/lib/qubes" ]; then
      [ -n "$qubes_vm_type" ] || qubes_vm_type="$(qubesdb-read /qubes-vm-type)"

Command qubesdb-read is unknown in VirtualBox, crashing whonix-firewall.

Recommended dependency tor-control-panel was accidentally removed. Will amend.

1 Like
16

Oh, what a bug. Another reason to solve Provide a cannoncial way to detect Qubes · Issue #1963 · QubesOS/qubes-issues · GitHub to prevent such very difficult to foreseeable issues.
I’ll think about replacing if [ -d "/usr/lib/qubes" ]; then with something better.

17

It could be if [ -d "/var/lib/qubes" ];. Seems less prone to be created.

By the way, we are using if [ -d "/usr/lib/qubes" ] in start-maybe, which is most likely why sdwdate-gui does not start in VirtualBox. That is the next debugging step.

1 Like
18

I think this is best

if command -v "qubesdb-read" >/dev/null 2>&1 ; then
19

Yes. Just read https://github.com/QubesOS/qubes-issues/issues/1963. This looks more robust.

1 Like
20

https://github.com/Whonix/Whonix/commit/01bee1d5540578fe45611176a6592f1562746ac8

21

Not sure if this is the best place to post, but I’ve been experiencing an issue with sdw-date gui widget on Qubes 4.2 using Whonix 17 for the last couple of days where no running workstation vm will show up in the sdw-date widget, only sys-whonix.

Is this the result of a planned change? I think it started happening after the last big Whonix 17 update (I think I’m on the testing repo). Should I be worried about this?

I’ve also been dealing with the problem described in the Qubes github issue #8672 (I can’t post links) regarding the gui widget.

Edit: just noticed this topic was 5 years old…my bad.

22

No.

Valid Compromise Indicators versus Invalid Compromise Indicators

23

Okay, but it seems that this is still relevant to the security of Qubes-Whonix, as it’s now not obvious if sdwdate has completed the synchronization for the workstation.

IIUC the new issue tracker is basically this forum; should I open a new topic for this issue, as it’s distinct from the one already reported to the qubes-os github?

24

No additional reports required.

25

This is probably fixed with this commit:

(Whonix is based on Kicksecure.)

This fix is now in all Whonix 17 repositories.

(This was fixed using “Instant Package Migration” (link).)

1 Like
26

Confirmed fixed by the update on my end, thank you!