Page MenuHomePhabricator

HulaHoop (HulaHoop)
UserAdministrator

Projects

User Details

User Since
Nov 21 2014, 10:16 PM (239 w, 2 d)
Roles
Administrator

Recent Activity

May 22 2019

HulaHoop added a comment to T901: package and test wiperam for Debian.

https://github.com/AvANa-BBS/freepto-lb/issues/53

May 22 2019, 7:42 AM · Whonix, Whonix-Host
HulaHoop added a comment to T803: coyIM.

@Patrick were you able to reproduce this? I wasn't

May 22 2019, 7:37 AM · Whonix 16, anon-meta-packages, Whonix
HulaHoop added a comment to T803: coyIM.

He was a major dev/creator of CoyIM but not the only one.

May 22 2019, 7:36 AM · Whonix 16, anon-meta-packages, Whonix
HulaHoop added a comment to T817: install jitterentropy by default.

His detailed reply:

May 22 2019, 7:34 AM · Whonix 15, Debian version 10 codename Buster, Whonix
HulaHoop added a comment to T720: post feature request for more secure clipboard sharing against VirtualBox and KVM.

Accepted as optional feature/usecase. Moved implementation design from protocol level to spice-gtk.

May 22 2019, 7:33 AM · VirtualBox, usability, Whonix

May 3 2019

HulaHoop added a comment to T670: Activating Lockdown.

Related thread on general kernel hardening:

May 3 2019, 6:14 PM · Debian version 10 codename Buster, Whonix

May 1 2019

HulaHoop added a comment to T817: install jitterentropy by default.

user@host:~/jitterentropy-20140131/tests_userspace/timing$ ./jitterentropy-inittest
Pass 10000 - Fail 0 - Rounds 10000

May 1 2019, 2:21 AM · Whonix 15, Debian version 10 codename Buster, Whonix

Apr 30 2019

HulaHoop added a comment to T720: post feature request for more secure clipboard sharing against VirtualBox and KVM.

https://gitlab.freedesktop.org/spice/spice-protocol/issues/8

Apr 30 2019, 11:52 PM · VirtualBox, usability, Whonix

Apr 25 2019

HulaHoop added a comment to T720: post feature request for more secure clipboard sharing against VirtualBox and KVM.

Issue was discussed by Libvirt devs on RedHat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1320263#c4
I even linked to a secure clipboard proposal that would have given a secure clipboard functionality by copying Qubes style interaction. It went no where and was closed as WONTFIX.

Apr 25 2019, 4:01 AM · VirtualBox, usability, Whonix

Apr 18 2019

HulaHoop added a comment to T769: Add LUKS container GUI or CLI utility by default.

I also added the cli version to the non-qubes-vm-enhancements-cli section. It is a dep of a gui install but not vice versa. Zulucrypt plugin package was added there too since enchancements-cli is a subset of enhancements-gui.

Apr 18 2019, 6:36 PM · Whonix 15, Debian version 10 codename Buster
HulaHoop added a comment to T769: Add LUKS container GUI or CLI utility by default.

https://github.com/Whonix/anon-meta-packages/pull/20/commits/0ab1a0aa4b5e22149286d6156a1816e3ca65626c

Apr 18 2019, 6:34 PM · Whonix 15, Debian version 10 codename Buster

Apr 17 2019

HulaHoop added a comment to T769: Add LUKS container GUI or CLI utility by default.

zulucrypt works in Buster. Tomb does not.

Apr 17 2019, 6:08 AM · Whonix 15, Debian version 10 codename Buster

Apr 14 2019

HulaHoop added a comment to T869: Install Firejail by default inside Whonix.

Then I am wondering if we ought to install any of the following recommended packages too?

Apr 14 2019, 5:01 AM · Whonix 15, firejail, Whonix

Apr 5 2019

HulaHoop added a comment to T543: TCP ISNs and Temperature induced clock skews.

@Patrick What is the status of integration? Since we have kloak this is also a great defense to have. There is a script on there for packing as a deb:

Apr 5 2019, 8:55 PM · C Code, security, Whonix

Mar 29 2019

HulaHoop added a comment to T670: Activating Lockdown.

Likely part of 5.2. We won't see it until the version after Buster unless we use backports.

Mar 29 2019, 4:39 AM · Debian version 10 codename Buster, Whonix

Mar 26 2019

HulaHoop added a comment to T878: remove mapaddress entries in torrc for 1.1.1.1 and 2.2.2.2 since these allow fingerprinting Whonix users.

Can you think of any other app besides a browser that parses JS/Remote code that can manipulate it into requesting those particular addresses?

Mar 26 2019, 6:04 PM · anon-gw-anonymizer-config, Whonix 15, anon-mixmaster, Whonix

Mar 25 2019

HulaHoop added a comment to T878: remove mapaddress entries in torrc for 1.1.1.1 and 2.2.2.2 since these allow fingerprinting Whonix users.

On a second thought I wonder if this is still a Whonix specific fingerprinting vector. Any DNS request for 172.24.0.0 would resolve to bshc44ac76q3kskw.onion. Not something a remote website could exploit?

Mar 25 2019, 8:39 PM · anon-gw-anonymizer-config, Whonix 15, anon-mixmaster, Whonix
HulaHoop added a comment to T878: remove mapaddress entries in torrc for 1.1.1.1 and 2.2.2.2 since these allow fingerprinting Whonix users.

@Patrick Now we have to figure out how or if we can use the version in sid on Buster since it is no longer available in stable-next after the freeze. Let me know what you think and I will open a ticket for it is doable.

Mar 25 2019, 12:35 AM · anon-gw-anonymizer-config, Whonix 15, anon-mixmaster, Whonix
HulaHoop added a comment to T878: remove mapaddress entries in torrc for 1.1.1.1 and 2.2.2.2 since these allow fingerprinting Whonix users.

https://github.com/Whonix/anon-gw-anonymizer-config/pull/17/commits/5351bd4765476e9522c77cea5a8e30e6c4f94083

Mar 25 2019, 12:33 AM · anon-gw-anonymizer-config, Whonix 15, anon-mixmaster, Whonix

Mar 22 2019

HulaHoop updated the task description for T769: Add LUKS container GUI or CLI utility by default.
Mar 22 2019, 11:41 PM · Whonix 15, Debian version 10 codename Buster
HulaHoop renamed T769: Add LUKS container GUI or CLI utility by default from Adding zulucrypt to Whonix to Add LUKS container GUI or CLI utility by default.
Mar 22 2019, 11:40 PM · Whonix 15, Debian version 10 codename Buster
HulaHoop added a comment to T769: Add LUKS container GUI or CLI utility by default.

Test the tomb LUKS container script as an alternative.

Mar 22 2019, 11:39 PM · Whonix 15, Debian version 10 codename Buster

Feb 21 2019

HulaHoop closed T893: Mouse cursor rarely works on KVM Whonix WS 14.0.1.3.8 as Resolved.

What distro are you using?

Feb 21 2019, 9:33 PM · KVM, Whonix

Feb 18 2019

HulaHoop added a comment to T878: remove mapaddress entries in torrc for 1.1.1.1 and 2.2.2.2 since these allow fingerprinting Whonix users.

Other imporvements in this thread such as functioning SMTP gateways are also part of this ticket:

Feb 18 2019, 7:01 PM · anon-gw-anonymizer-config, Whonix 15, anon-mixmaster, Whonix
HulaHoop added a comment to T580: Document recovery procedure after compromise.

Good for the time being, if anyone wants to add more there is an outline of what procedures can be done, to add to.

Feb 18 2019, 6:57 PM · Whonix, user documentation
HulaHoop closed T580: Document recovery procedure after compromise as Resolved.
Feb 18 2019, 6:57 PM · Whonix, user documentation

Feb 2 2019

HulaHoop closed T544: systemd-socket-proxyd instructions template as Resolved.
Feb 2 2019, 8:57 PM · Whonix 15, user documentation, Whonix, design documentation
HulaHoop added a comment to T544: systemd-socket-proxyd instructions template.

I created a user documentation page explaining this feature and when to use it for users to understand.

Feb 2 2019, 8:56 PM · Whonix 15, user documentation, Whonix, design documentation
HulaHoop added a comment to T769: Add LUKS container GUI or CLI utility by default.

Moved to xfce so past comment is irrelevant. Will test Zulu after moving to Buster and add if it works.

Feb 2 2019, 3:49 AM · Whonix 15, Debian version 10 codename Buster
HulaHoop added a comment to T544: systemd-socket-proxyd instructions template.

@Patrick Was this only relevant for Retroshare?

Feb 2 2019, 3:48 AM · Whonix 15, user documentation, Whonix, design documentation
HulaHoop closed T567: research: Single Tor-Gateway with Multiple Workstations vs Multiple Tor-Gateways mapped 1:1 to Workstation VMs as Resolved.

The concept was documented for operational use. Auto Guard de-duplication considered too complex to deploy and manual checking is enough.

Feb 2 2019, 3:47 AM · research, Whonix, user documentation
HulaHoop added a comment to T892: Mixmaster replacement remailer stat lists.

Mixmaster is not present in Buster BTW

Feb 2 2019, 3:45 AM · Whonix
HulaHoop closed T892: Mixmaster replacement remailer stat lists as Invalid.

Looks like someone beat us to it:

Feb 2 2019, 3:43 AM · Whonix
HulaHoop added a comment to T580: Document recovery procedure after compromise.

Ready to close if happy.

Feb 2 2019, 3:39 AM · Whonix, user documentation
HulaHoop added a comment to T878: remove mapaddress entries in torrc for 1.1.1.1 and 2.2.2.2 since these allow fingerprinting Whonix users.

Middle of the range solution. How does this sound? Confirmed it falls within the private address CIDR:

Feb 2 2019, 3:36 AM · anon-gw-anonymizer-config, Whonix 15, anon-mixmaster, Whonix

Jan 31 2019

HulaHoop updated the task description for T892: Mixmaster replacement remailer stat lists.
Jan 31 2019, 2:20 AM · Whonix
HulaHoop triaged T892: Mixmaster replacement remailer stat lists as Normal priority.
Jan 31 2019, 2:17 AM · Whonix

Jan 21 2019

HulaHoop added a comment to T721: deb.debian.org instead of us.debian.org and use https (SSL, TLS) by default / fix build --connection onion.

Building initiates. I had these deps installed anyhow. Unpinning the CPU resolved some early build error, but now it craps out at RAW image creation. Not really related to your inquiry.

Jan 21 2019, 10:32 PM · anon-apt-sources-list, Whonix

Jan 13 2019

HulaHoop added a comment to T885: Add MAT2 to Whonix 15 / Debian buster.

Seems so. This one is a context menu option or commandline but it supports a lot more stuff than the original and it pulls in other specialized tools to do the work.

Jan 13 2019, 2:00 AM · Debian version 10 codename Buster, Whonix, Whonix 15
HulaHoop added a comment to T523: document identity correlation attacks and defenses / Removing Apache Recommendation.

Done

Jan 13 2019, 1:56 AM · Whonix 14, Whonix, user documentation, research

Jan 11 2019

HulaHoop reopened T595: install onionshare by default in Whonix 15 as "Open".

Onionshare is in Buster.
https://packages.debian.org/buster/onionshare

Jan 11 2019, 7:46 PM · Whonix 15, Debian version 10 codename Buster, Whonix, anon-meta-packages, usability

Jan 4 2019

HulaHoop added a comment to T523: document identity correlation attacks and defenses / Removing Apache Recommendation.

Done. You can close this ticket once you agree with edits.

Jan 4 2019, 5:58 PM · Whonix 14, Whonix, user documentation, research

Dec 28 2018

HulaHoop added a comment to T523: document identity correlation attacks and defenses / Removing Apache Recommendation.

From this size comparison on Debian wiki, I think the best and most secure option is the smallest and most minimal one: micro-httpd

Dec 28 2018, 8:31 PM · Whonix 14, Whonix, user documentation, research
HulaHoop added a comment to T721: deb.debian.org instead of us.debian.org and use https (SSL, TLS) by default / fix build --connection onion.
Dec 28 2018, 1:04 AM · anon-apt-sources-list, Whonix

Dec 5 2018

HulaHoop added a comment to T878: remove mapaddress entries in torrc for 1.1.1.1 and 2.2.2.2 since these allow fingerprinting Whonix users.

My advice is to use a private address range reserved for this purpose by IANA. These will never be used in the future by anyone. Sine we use 10.x.x.x and moved away from 192.x.x.x, this leaves 172.x.x.x

Dec 5 2018, 12:13 AM · anon-gw-anonymizer-config, Whonix 15, anon-mixmaster, Whonix

Dec 3 2018

HulaHoop added a comment to T881: remove attempts to hide CPU information from VM in VirtualBox.

There's been research showing that trying to hide CPU information in a virtualizer is futile.

Dec 3 2018, 7:07 PM · build, VirtualBox, Whonix 15, Whonix, Whonix 14
HulaHoop added a comment to T71: Show desktop clock in local time; keep system in UTC.

I think hiding the clock is a bad idea as a user may want to manually run sdwdate to adjust it if it's out of whack before initiating internet traffic. (This is on non-Qubes versions lacking auto time adjust)

Dec 3 2018, 6:15 PM · research, whonix-setup-wizard, usability, desktop, Whonix
HulaHoop added a comment to T509: Consider nftables as a replacement for iptables.

https://researchut.com/post/migrating-firewall-to-nftables/

Dec 3 2018, 6:02 PM · iptables, vpn-firewall, whonix-ws-firewall, whonix-gw-firewall, Whonix, refactoring, research

Oct 28 2018

HulaHoop added a comment to T804: ParrotOS's Firejail Code.

I disagree. Firetools makes administration easier and has a place on both VMs.

Oct 28 2018, 4:49 AM · Whonix 16, Whonix

Oct 13 2018

HulaHoop added a comment to T80: direct SSL certificate pinning for check.torproject.org and torproject.org (curl method).

We can now grab the browser tarball from the TPO onion instead which makes this ticket obsolete. Close if you concur.

Oct 13 2018, 2:47 PM · Whonix, whonixcheck, tb-updater, security
HulaHoop added a comment to T567: research: Single Tor-Gateway with Multiple Workstations vs Multiple Tor-Gateways mapped 1:1 to Workstation VMs.

Proposed implementations for multi-Tor suggested here:

Oct 13 2018, 12:44 AM · research, Whonix, user documentation
HulaHoop added a comment to T567: research: Single Tor-Gateway with Multiple Workstations vs Multiple Tor-Gateways mapped 1:1 to Workstation VMs.

The short story is that things get worse very quickly, but there is hope.
The analysis below assumes only the adversary that runs guards and not the local adversary like the host OS or the Whonix processes themselves.
In my analysis I assume a hypothetical adversarial guard bandwidth of 10% of the entire network. This is an arbitrary number since we don't know the real number, but it serves to show the trends as we increase the guards per client and number of clients per user. I do the kind of analysis we do in the Conflux[1] paper which is very relevant here, especially Table 3 and its discussion in section 5.2. I update the numbers and extend that analysis for the scenarios you have described.

  1. 1 guard/client, 1 client/user.

The adversary (i,e, the compromised guard) will have the ability to observe 10% of the clients and hence 10% users. This is the situation today.

  1. 2 guards/client, 1 client/user.

This is worse than 1 above. There is now a 18% probability that only one of the guards is compromised per client and a 1% chance that two guards are compromised per client. The probability of at least one bad guard is hence 19%. There really is not a real distinction between one or two bad guards from the user perspective since in both situations the client will go through a malicious guard in a short period of time, since the guard is picked uniformly at random from the guard set.

  1. 1 guard/client, 2 clients/user.

The observable clients again increase to 19% from the base 10% in 1 above. This means that if the user split her app (or group of apps) across the clients then there is a 19% chance that at least one of the app (groups) is compromised. However, for each client there is still only a 10% chance that a malicious guard is present. Is this configuration better than scenario 2 above? Perhaps, but let's look at the following scenario first.

  1. 2 guards/client, 2 clients/user.

The observable clients increases to 54%. This means that there is a 54% chance that at least one bad guard is present. This is worse than all the other scenarios above. However, if we fix apps (or groups of apps) to particular clients then we can compare to scenario 2 where the app group/client is analogous and the same analysis holds. Then, for each client there is again a 19% chance that there is a malicious guard present. If we compare to 3 above we can see that if we only use 1 guard/client then we can drop the exposure back down to 10% for that client and hence app group.
Taking the above into account we can get good results by keeping the guard set size to 1 and users spin up one client for each app. Then we can achieve at most 10% of apps compromised at *any given time* but not simultaneously. We can call this scenario (which is an extension of scenario 3) the 1 guard/app scenario (1G/A). See the appendix for more tweaks to decrease guard exposure.
If we want to consider 1G/A, then the next question for your user base is that is it better to either 1) have some portion of your apps compromised at *all* times (scenario 1G/A) or 2) have *all* your apps compromised some portion of the time (scenario 1). Tor tends to bend towards option 2, but then they have not considered the option of multi-client usage since it doesn't improve the situation in a non-compartmentalized setting, unlike the Whonix situation. I believe that option 2 is flawed because you never know if you are in fact currently compromised or not. It might be better to go ahead with assuming that you are compromised and mitigating that compromise to some portion of your network activity than all or nothing, which is what option 1 provides.
I hope that answers your questions. Please do not hesitate to get in touch again if you would like to discuss further. I think this is a very interesting problem area and would be happy to contribute to improving the situation.
Best regards,
Tariq Elahi
[1] http://cacr.uwaterloo.ca/techreports/2013/cacr2013-16.pdf
Appendix
We can do better if we allow a user's clients to look at each other's lists to exclude guards that are already picked. The benefit would be that once the bad bandwith has been assigned it can no longer affect subsequent guard selections. However, clients looking at each other's memory space will compromise your vision of process containment. A zero knowledge/oblivious method for comparing guard lists might work to avoid this problem, and indeed the adversarial response will be weak since the best they can do is spread their bad bandwidth over many relays and at best return to the original exposure rate (e.g. 10%) but now with added costs of running many more relays.

Oct 13 2018, 12:42 AM · research, Whonix, user documentation
HulaHoop closed T872: mouse does not work in Whonix-Workstation 14 KVM as Invalid.

Sorry not reproducible on my end. May be related to the fact that you are running a non-standard setup with custom compiled binaries. By running packages from your distro there is a higher chance that bugs are more visible for more people and more likely to be fixed.

Oct 13 2018, 12:37 AM · Whonix, Whonix 14, KVM

Oct 12 2018

HulaHoop closed T869: Install Firejail by default inside Whonix as Resolved.

Closing. duplicate of:

Oct 12 2018, 12:21 AM · Whonix 15, firejail, Whonix
HulaHoop closed T873: Remove Ricochet from Whonix as Invalid.

There is nothing dead about it. I jsut explained this on the forum. It is perfectly workable and openprivacy is owrking on creating a P2P asynchronous chat solution over its protocol.

Oct 12 2018, 12:15 AM · Whonix 15, Whonix
HulaHoop added a comment to T869: Install Firejail by default inside Whonix.

It's on the roadmap but a little far off until ParrotOS changes can be combined with the upstream package. It will make maintenance and turning it on by default much more easier.

Oct 12 2018, 12:12 AM · Whonix 15, firejail, Whonix
HulaHoop added a comment to T872: mouse does not work in Whonix-Workstation 14 KVM.

It could be the VM is confused because apparently there are two types of mice attached. I assumed that by adding virtio-mouse it would override and replace the emulated one. Turns out its not this way and I went ahead and reverted this config which should be effective in the next release.

Oct 12 2018, 12:11 AM · Whonix, Whonix 14, KVM

Oct 4 2018

HulaHoop added a comment to T837: create Whonix project accounts.

@TNTBOMBOM I added a few more sites in a second paragraph first ticket. Please create the accounts when you have time.

Oct 4 2018, 3:12 PM · outreach, Whonix
HulaHoop updated the task description for T837: create Whonix project accounts.
Oct 4 2018, 3:11 PM · outreach, Whonix

Sep 17 2018

HulaHoop renamed T819: persistent / live mode indicator systray - graphical indication on the desktop that system is running in live mode vs persistent mode from persistent / love mode indicator systray - graphical indication on the desktop that system is running in live mode vs persistent mode to persistent / live mode indicator systray - graphical indication on the desktop that system is running in live mode vs persistent mode.
Sep 17 2018, 3:06 AM · live-mode, Whonix

Sep 14 2018

HulaHoop added a comment to T769: Add LUKS container GUI or CLI utility by default.

Test out the (LUKS wrapper) Tomb implementation in KDE Vault. Should be around by Buster.

Sep 14 2018, 3:46 AM · Whonix 15, Debian version 10 codename Buster

Sep 11 2018

HulaHoop triaged T833: Software to inlcude from backports as Normal priority.
Sep 11 2018, 7:38 PM · anon-apt-sources-list, Whonix 16, Whonix
HulaHoop triaged T832: sdwdate support for GETINFO “current-time/{local,utc}” as Normal priority.
Sep 11 2018, 7:32 PM · sdwdate-server, sdwdate, Whonix

Aug 17 2018

HulaHoop added a comment to T544: systemd-socket-proxyd instructions template.

Template created: https://www.whonix.org/wiki/Template:Systemd-socket-proxyd

Aug 17 2018, 8:39 PM · Whonix 15, user documentation, Whonix, design documentation
HulaHoop added a comment to T803: coyIM.

Offtopic: There is a PR from Algernon for intramfs packages, what s their status?

Aug 17 2018, 5:53 PM · Whonix 16, anon-meta-packages, Whonix
HulaHoop triaged T820: Missing pinentry-qt as Normal priority.
Aug 17 2018, 4:48 PM · Whonix 15, Whonix 14, Whonix, bug

Aug 16 2018

HulaHoop closed T367: Mixmaster GUI Options as Wontfix.

Non-Debian dependencies and non materialization of TUF PyPi makes a secure way to obtain this package impossible.

Aug 16 2018, 5:42 PM · user documentation, research, usability, Whonix
HulaHoop lowered the priority of T560: finish RetroShare over Tor port redirection instructions from Low to Wishlist.
Aug 16 2018, 5:27 PM · user documentation, Whonix
HulaHoop edited projects for T769: Add LUKS container GUI or CLI utility by default, added: Debian version 10 codename Buster; removed Whonix 15.
Aug 16 2018, 5:24 PM · Whonix 15, Debian version 10 codename Buster
HulaHoop placed T600: Integrating Guix/Nix Package Manager up for grabs.
Aug 16 2018, 5:16 PM · Whonix, packaging, research
HulaHoop placed T772: Managing programs without Tor Socks / DNS Support up for grabs.
Aug 16 2018, 5:15 PM · research

Aug 15 2018

HulaHoop added a comment to T803: coyIM.

Old pull request:
https://github.com/Whonix/anon-meta-packages/pull/8

Aug 15 2018, 7:33 PM · Whonix 16, anon-meta-packages, Whonix

Aug 12 2018

HulaHoop added a comment to T803: coyIM.

Done. Connects successfully even when Transparent TCP/DNS disabled on gateway. So it uses stream isolation out of the box and is ready for prime time.

Aug 12 2018, 7:07 PM · Whonix 16, anon-meta-packages, Whonix

Aug 10 2018

HulaHoop added a comment to T803: coyIM.

So what task remains for this DNS/TransPort leak testing?

Aug 10 2018, 4:38 PM · Whonix 16, anon-meta-packages, Whonix
HulaHoop reopened T596: keep an eye on kloak anti keystroke deanonymization tool as "Open".

He was busy those past few months and thought there was no interest. @Patrick Expect a new release this coming week.

Aug 10 2018, 4:37 PM · Whonix 16, security, Whonix

Aug 9 2018

HulaHoop added a comment to T596: keep an eye on kloak anti keystroke deanonymization tool.

Ping:
https://github.com/vmonaco/kloak/issues/10

Aug 9 2018, 9:37 PM · Whonix 16, security, Whonix

Aug 8 2018

HulaHoop added a comment to T596: keep an eye on kloak anti keystroke deanonymization tool.

Why not ping him first? Its a waste of good work otherwise.

Aug 8 2018, 4:55 PM · Whonix 16, security, Whonix

Aug 7 2018

HulaHoop added a comment to T815: sclockadj fingerprinting defense - set time using sclockadj the same way NTP / sntp / chrony / systemd-timesyncd is changing the clock.

In theory, we could make sdwdate provide a local (default) (or optional opt-in server) NTP compatible time provider. Could be useful anyhow. -> sdwdate-server No idea how hard that would be.
And then configure NTP to connect only to that local NTP server.

Aug 7 2018, 8:37 AM · Whonix, C Code, sclockadj, sdwdate
HulaHoop closed T814: find out what the most popular time synchronization daemon is / find out debian's default time synchronization daemon as Resolved.
Aug 7 2018, 8:16 AM · Whonix, Whonix 15, sclockadj, sdwdate
HulaHoop closed T814: find out what the most popular time synchronization daemon is / find out debian's default time synchronization daemon, a subtask of T815: sclockadj fingerprinting defense - set time using sclockadj the same way NTP / sntp / chrony / systemd-timesyncd is changing the clock, as Resolved.
Aug 7 2018, 8:16 AM · Whonix, C Code, sclockadj, sdwdate
HulaHoop closed T798: VLC X11 Decoding by default as Resolved.
Aug 7 2018, 8:16 AM · anon-apps-config, Whonix 15, Whonix

Aug 6 2018

HulaHoop added a comment to T815: sclockadj fingerprinting defense - set time using sclockadj the same way NTP / sntp / chrony / systemd-timesyncd is changing the clock.

The easy way: calculating the offset between local time and the onion average in timesync then using ntpdate's slew option if the offset is less than 0.5s. Otherwise you tell it to step up the time immediately so that you are accurately mimicking the default behavior. However you can force slewing all the time with -B. This way you won't need to touch kernel syscalls as ntpdate should be able to do the operation for you.

Aug 6 2018, 8:28 PM · Whonix, C Code, sclockadj, sdwdate
HulaHoop added a comment to T815: sclockadj fingerprinting defense - set time using sclockadj the same way NTP / sntp / chrony / systemd-timesyncd is changing the clock.

From what I understand, this code path is only relevant when timesyncd is talking directly with NTP servers and reacting to replies about deltas between local and remote times. There is no way you can call that function from the command line when using timedatectl standalone AFAICT.

Aug 6 2018, 5:46 PM · Whonix, C Code, sclockadj, sdwdate

Aug 3 2018

HulaHoop added a comment to T727: solve the Xen entropy scarcity problem / implement something like virtio-rng into Xen upstream.

Playing devil's advocate here: Ted Ts'o [0] expresses strong skepticism about the efficacy of RNGs that rely on CPU jitter. summary: CPU jitter may not be random as thought to someone who designed the CPU cache and know how its internals "tick" [1]. So while these RNGs may not harm, another solution for RNG-less platforms may be a good idea.

Aug 3 2018, 6:10 AM · security, Qubes, Whonix
HulaHoop added a comment to T727: solve the Xen entropy scarcity problem / implement something like virtio-rng into Xen upstream.

An interesting implementation to work around early boot entropy scarcity with havegedis to include it in the initrd. May be hackish but could be easier for Marmarek than writing something at the EFI level.

Aug 3 2018, 5:53 AM · security, Qubes, Whonix
HulaHoop added a comment to T727: solve the Xen entropy scarcity problem / implement something like virtio-rng into Xen upstream.

Done. Asked about Xen too but they may not be familiar with its innards. You may want to contact the Xen devs directly using my message as a template.

Aug 3 2018, 5:34 AM · security, Qubes, Whonix

Aug 2 2018

HulaHoop added a comment to T727: solve the Xen entropy scarcity problem / implement something like virtio-rng into Xen upstream.

I think its worth asking the hypervisor devs if this applies for the platforms we care about.

Aug 2 2018, 5:33 AM · security, Qubes, Whonix

Jul 31 2018

HulaHoop added a comment to T727: solve the Xen entropy scarcity problem / implement something like virtio-rng into Xen upstream.

jitterentropy-rng should solve this and is a mainline Linux solution that works the same way haveged does. Please see: https://phabricator.whonix.org/T817

Jul 31 2018, 4:23 AM · security, Qubes, Whonix
HulaHoop triaged T817: install jitterentropy by default as Normal priority.
Jul 31 2018, 4:22 AM · Whonix 15, Debian version 10 codename Buster, Whonix

Jul 27 2018

HulaHoop added a comment to T815: sclockadj fingerprinting defense - set time using sclockadj the same way NTP / sntp / chrony / systemd-timesyncd is changing the clock.

Since we are interested in ntpd's default behavior (for blending in purposes) it turns out that it performs instant clock jumps once the delta difference is excessively large otherwise its slewing algorithm would take forever to adjust the time.

Jul 27 2018, 7:33 PM · Whonix, C Code, sclockadj, sdwdate
HulaHoop added a comment to T815: sclockadj fingerprinting defense - set time using sclockadj the same way NTP / sntp / chrony / systemd-timesyncd is changing the clock.

It doesn't seem that timedatectl supports gradual time adjustment. Our next best option is ntpd which can do so but cannot coexist with timedatectl - we can only run either but not both. According to popcon, ntpd is the mos widely used time daemon so its the natural choice.

Jul 27 2018, 6:22 PM · Whonix, C Code, sclockadj, sdwdate

Jul 25 2018

HulaHoop added a comment to T815: sclockadj fingerprinting defense - set time using sclockadj the same way NTP / sntp / chrony / systemd-timesyncd is changing the clock.

the time could be set with timedatectl by feeding it the time with this command:

Jul 25 2018, 9:20 PM · Whonix, C Code, sclockadj, sdwdate
HulaHoop added a comment to T814: find out what the most popular time synchronization daemon is / find out debian's default time synchronization daemon.

Stretch+ uses systemd-timesyncd by default therefore its the most popular.

Jul 25 2018, 8:38 PM · Whonix, Whonix 15, sclockadj, sdwdate
HulaHoop triaged T813: Onion Vanguard Security plugin as Normal priority.
Jul 25 2018, 2:01 AM · Whonix

Jul 22 2018

HulaHoop added a comment to T600: Integrating Guix/Nix Package Manager.

@ng0 I wrote a proposal draft. Feel free to improve it before I post:

Jul 22 2018, 6:23 PM · Whonix, packaging, research

Jun 30 2018

HulaHoop added a comment to T798: VLC X11 Decoding by default.

https://github.com/Whonix/anon-apps-config/pull/4/commits/295b0702221cb4bc2116379fe0861cc6367bfa22

Jun 30 2018, 11:52 PM · anon-apps-config, Whonix 15, Whonix

Jun 29 2018

HulaHoop added a comment to T801: use libresolv-wrapper rather than functional Whonix-Gateway system DNS resolver?.

Check these alternatives out:

Jun 29 2018, 11:58 PM · Whonix, Whonix 16, research, anon-gw-dns-conf
HulaHoop added a comment to T798: VLC X11 Decoding by default.

OK did so there

Jun 29 2018, 11:34 PM · anon-apps-config, Whonix 15, Whonix

Jun 26 2018

HulaHoop triaged T806: Preload and similar performance tuneups as Normal priority.
Jun 26 2018, 7:20 AM · Whonix
HulaHoop triaged T805: cwtch as Normal priority.
Jun 26 2018, 7:16 AM · Whonix