Page MenuHomePhabricator

dau (Felipe Dau)
User

Projects

User does not belong to any projects.

User Details

User Since
Jul 2 2015, 8:47 PM (179 w, 3 d)

Recent Activity

May 30 2017

dau added a comment to T654: create an unMessage onion-grater profile.

I talked to meejah and GETCONF SOCKSPort is only issued when it fails to use the port that was provided or the default ones. I think we could allow that and leave it up to txtorcon to query the process the right SOCKS port. That will make it easier for us to implement the automatic Tor process handling (one less thing to ask the user).

May 30 2017, 10:32 PM · Whonix, onion-grater (Control Port Filter Proxy)

May 28 2017

dau added a comment to T654: create an unMessage onion-grater profile.

Here is an update, based on the profile you provided and Ricochet's:

May 28 2017, 7:40 PM · Whonix, onion-grater (Control Port Filter Proxy)

May 17 2017

dau added a comment to T659: Publish "Listen Port Convention".
In T659#13291, @Patrick wrote:

Yes. Our forum is using discourse (Libre Software forum software).

May 17 2017, 1:56 AM · Whonix

May 16 2017

dau added a comment to T659: Publish "Listen Port Convention".
In T659#13289, @Patrick wrote:

Not required for this very task, however very much welcome for your Whonix interest generally.

May 16 2017, 9:40 PM · Whonix
dau added a comment to T659: Publish "Listen Port Convention".

I just checked some options and saved a draft. Let me know if you need a link or something to find it.

May 16 2017, 8:53 PM · Whonix

May 13 2017

dau added a comment to T674: phabricator replies by e-mail issue coming from noreply@phabricator.whonix.org.

Was the text you sent exactly the following?

May 13 2017, 2:42 PM · Whonix, phabricator
dau added a comment to T659: Publish "Listen Port Convention".
In T659#13246, @Patrick wrote:

May I assign this to you?

May 13 2017, 3:19 AM · Whonix

May 9 2017

dau added a comment to T674: phabricator replies by e-mail issue coming from noreply@phabricator.whonix.org.

Correct, I receive notifications from noreply@phabricator.whonix.org. The reply was indeed sent

May 9 2017, 5:22 AM · Whonix, phabricator

May 3 2017

dau added a comment to T668: Create a spec for composing proposals/specs.

I just updated the text a bit with your feedback.

May 3 2017, 1:09 AM · Whonix
dau updated the task description for T668: Create a spec for composing proposals/specs.
May 3 2017, 1:07 AM · Whonix

May 1 2017

dau added a comment to T668: Create a spec for composing proposals/specs.

On Mon, May 01, 2017 at 01:03:57AM +0000, Patrick (Patrick Schleizer) wrote:

XXX Should we use the usernames from Phabricator?

Probably not. But with higher priority, I'd leave that decision to the contributor.

May 1 2017, 7:17 PM · Whonix
dau added a comment to T659: Publish "Listen Port Convention".

I tried to reply, but here is what I got:

May 1 2017, 7:14 PM · Whonix

Apr 30 2017

dau updated the task description for T668: Create a spec for composing proposals/specs.
Apr 30 2017, 11:06 PM · Whonix
dau added a comment to T659: Publish "Listen Port Convention".
In T659#13135, @Patrick wrote:

dau (Felipe Dau):

(Should this be discussed in another ticket?)

You can if there are additional questions, sure.

Apr 30 2017, 10:56 PM · Whonix
dau created T669: Open a Debian ticket for the "Listen Port Convention".
Apr 30 2017, 10:55 PM · Debian version 10 codename Buster, Whonix
dau created T668: Create a spec for composing proposals/specs.
Apr 30 2017, 10:42 PM · Whonix
dau added a comment to T659: Publish "Listen Port Convention".
In T659#13130, @Patrick wrote:

Right. From that perspective, we should probably rename the repository
to specs with a sub folder proposals.

example:
https://gitweb.torproject.org/torspec.git/tree/proposals/115-two-hop-paths.txt

Filename: 115-two-hop-paths.txt
Title: Two Hop Paths
Author: Mike Perry
Created:
Status: Dead
Supersedes: 112

Or we don't use sub folders - then the file name would stay the same.
And just use a header to document the status and remaining to do.

I am just unsure if in the future it will be useful to separate them
to know what is stable/accepted/etc and what is not. Should we worry
about that later?

Let's just take our best guess. There is a lot of freedom in these options.

Apr 30 2017, 7:59 AM · Whonix

Apr 29 2017

dau added a comment to T659: Publish "Listen Port Convention".
In T659#13045, @Patrick wrote:

Should this be moved out of proposals/?

I am neutral. If you like, go for it.

(In comparison, RFC - they keep calling them RFCs.)

Apr 29 2017, 7:54 PM · Whonix
dau updated the task description for T659: Publish "Listen Port Convention".
Apr 29 2017, 7:45 PM · Whonix
dau updated the task description for T660: Implement "Listen Port Convention" on Whonix.
Apr 29 2017, 7:45 PM · Whonix

Apr 24 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.

Sorry for taking a long time to open these:

Apr 24 2017, 5:32 AM · research, Whonix, upstream, Whonix 14
dau created T661: Implement a config parser.
Apr 24 2017, 5:29 AM · Whonix
dau created T660: Implement "Listen Port Convention" on Whonix.
Apr 24 2017, 5:29 AM · Whonix
dau created T659: Publish "Listen Port Convention".
Apr 24 2017, 5:29 AM · Whonix

Apr 18 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
  • Find a place to "officially" publish the convention (has it moved from "proposal" to "convention"?)
Apr 18 2017, 12:39 AM · research, Whonix, upstream, Whonix 14
dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12974, @Patrick wrote:

The original write draft for local listener standard on debian-devel seems done.

Could you please kindly close this ticket / create follow up ticket(s)?

Apr 18 2017, 12:35 AM · research, Whonix, upstream, Whonix 14

Apr 13 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12944, @Patrick wrote:

json is not trivially parsed in shell scripts. For shell scripts, something that can be simply evaluated would be nice. (Just echo listen_ip=xxx, so listen_ip=xxx gets set.)

Hmm, maybe I was not very clear on the explanation. I did not suggest changing the configs format (the .conf files). They should still look like something evaluable.

I did not interpret your suggestion as a change in the conf files.

What I suggested was the use of json to return the *parsed* configs to applications.

Yes, got that. That's why I wanted to point out, that json is hard to parse in shell scripts.

As a Python user (and as this would be a Python package) I would expect to get a dict with the configs to use on my application. For non-Python applications, that dict would be serialized to json because I believe that is one of the most popular formats these days with support from many languages. Also, we can offer multiple "serializers" if needed.

Yes, something that works for shell scripts would be nice.

Was that your concern?

Yes.

Apr 13 2017, 11:36 AM · research, Whonix, upstream, Whonix 14

Apr 12 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12941, @Patrick wrote:

Perhaps
check_filename -> is_config_file
find_files -> find_config_files
?

On the other hand... I personally prefer the very at the end and to have some consistency, i.e. config_read, config_check and so forth.

Apr 12 2017, 10:53 PM · research, Whonix, upstream, Whonix 14

Apr 9 2017

dau added a comment to T634: write draft for stackable wrappers on debian-devel.

I noticed the link in the description needs to be updated. Would you change to https://github.com/Whonix/proposals/blob/master/634-stackable-wrappers.txt?

Apr 9 2017, 1:28 AM · Whonix, upstream
dau added a comment to T635: write draft for local listener standard on debian-devel.

This class is reasonably flexible so that people are able to customize how files are found and parsed. I pretty much just wrote the API, but here is what I have in mind:

Apr 9 2017, 1:25 AM · research, Whonix, upstream, Whonix 14

Mar 29 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.

I see. I will let you know how that goes.

Mar 29 2017, 2:32 AM · research, Whonix, upstream, Whonix 14

Mar 28 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12865, @Patrick wrote:

I have no idea if something like this exists. Might not as I don't know python applications doing this.

Mar 28 2017, 10:11 PM · research, Whonix, upstream, Whonix 14
dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12847, @Patrick wrote:

I think [zzz] is a bonus. No need to wait for it or to let it block our progress here. We got some great suggestions for our initial draft which we then implemented. I think in this case it's fair to interpret the absence of criticism and praise as an okay signal to move forward. This is probably also how things work. Some people create some convention, then just do it. If it then proves to be useful and working, it might become an official Debian standard. Neither Debian nor freedesktop want to be the gatekeepers of innovation.

Mar 28 2017, 9:12 PM · research, Whonix, upstream, Whonix 14
dau added a comment to T635: write draft for local listener standard on debian-devel.
Hi Patrick,
Mar 28 2017, 2:30 AM · research, Whonix, upstream, Whonix 14

Mar 26 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12834, @Patrick wrote:

Sent.

Mar 26 2017, 7:12 PM · research, Whonix, upstream, Whonix 14

Mar 23 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12825, @Patrick wrote:

Looks great!

Mar 23 2017, 8:35 PM · research, Whonix, upstream, Whonix 14

Mar 22 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12823, @Patrick wrote:

Right. Could you please add that text the Description part? I mean, the Description part is the part that gets actually copied over to the Debian mailing list in this case.

I'd suggest to add the link to the ticket and repo rather as a bonus. To be added somewhere at the end. We are mainly addressing the people on the mailing list. Beginning the text with two external links, I mean with...

might deter readers? Or am I over thinking this? I don't want to start painting the proverbial bikeshed.

Mar 22 2017, 11:11 AM · research, Whonix, upstream, Whonix 14
dau added a comment to T635: write draft for local listener standard on debian-devel.

Let me know what you think of the new PR.

Mar 22 2017, 3:40 AM · research, Whonix, upstream, Whonix 14
dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12809, @Patrick wrote:

Neither /etc/server-config.d nor /etc/server look like ideal choices
for folder names to me. I was hoping for better suggestions. =)

/etc/server/main.config is not so pretty. A folder with a single
config file. Why a folder then.

(I also had in mind /etc/listen/main.conf as well as
/etc/listen/conf.d/*.conf. That would be similar to /etc/dpkg. But
/etc/listen/conf.d/ would be less consistent with /usr/lib/listen.d/.)

What about as name, listen? Is this specific enough only on the topic
of listen or will it likely expand to also covering "server"?

Let's go with the following?

  • /etc/listen.conf
  • /etc/listen.d/*.conf
  • /usr/local/etc/listen.d/*.conf
  • /usr/lib/listen.d/*.conf
Mar 22 2017, 12:59 AM · research, Whonix, upstream, Whonix 14
dau added a comment to T634: write draft for stackable wrappers on debian-devel.
In T634#12810, @Patrick wrote:

Added How the wrappers would be specified in the config language is yet to be invented, which will be done if this implementation path looks favorable. does that sound alright to you?

Mar 22 2017, 12:36 AM · Whonix, upstream

Mar 21 2017

dau added a comment to T634: write draft for stackable wrappers on debian-devel.
In T634#12793, @Patrick wrote:

Right. (Feel free to report a bug against http://trac.torproject.org torsocks component.)

Mar 21 2017, 9:22 PM · Whonix, upstream
dau added a comment to T635: write draft for local listener standard on debian-devel.

Alright, I just made the PR with the changes we discussed. Also made minor changes to make it a bit more friendlier.

Mar 21 2017, 9:18 PM · research, Whonix, upstream, Whonix 14
dau added a comment to T634: write draft for stackable wrappers on debian-devel.
In T634#12786, @Patrick wrote:

Any and torsocks leak issues are torsocks' bugs.

Mar 21 2017, 2:26 AM · Whonix, upstream
dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12787, @Patrick wrote:

If you are using git anyhow to generate the diff, could you please fork https://github.com/adrelanos/listen-port-convention and commit? That would make the diff a lot easier to apply and read for me.

Mar 21 2017, 1:42 AM · research, Whonix, upstream, Whonix 14

Mar 20 2017

dau added a comment to T634: write draft for stackable wrappers on debian-devel.

This is a great idea!

Mar 20 2017, 3:21 AM · Whonix, upstream
dau added a comment to T635: write draft for local listener standard on debian-devel.

As we discussed in [0], I am updating the draft.

Mar 20 2017, 2:14 AM · research, Whonix, upstream, Whonix 14

Feb 21 2017

dau added a comment to T622: Run unMessage on Whonix.

I waited for the Tor PR guys to get back to me but I'm pretty sure they won't at this point. I went ahead and announced it on our blog and other high traffic mail lists to get more attention.

https://www.whonix.org/blog/announcing-unmessage-next-gen-tor-messenger
https://lists.torproject.org/pipermail/tor-talk/2017-February/042954.html
https://mailman.stanford.edu/pipermail/liberationtech/2017-February/016882.html

Feb 21 2017, 10:36 PM · Whonix
dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12405, @Patrick wrote:

Thank you for your feedback!

Feb 21 2017, 1:11 AM · research, Whonix, upstream, Whonix 14

Feb 20 2017

dau added a comment to T635: write draft for local listener standard on debian-devel.
In T635#12393, @Patrick wrote:

a) is how systemd parses systemd unit files. In that case one would have to use listen_ip= to disable listeners by lower priority configuration files.

Feb 20 2017, 8:55 PM · research, Whonix, upstream, Whonix 14
dau added a comment to T635: write draft for local listener standard on debian-devel.

I agree, this looks great! The only thing I noticed is that the dpkg conflict resolution reference is probably missing a :. Maybe that's why it looks like a checked check box? ([x] instead of [x]:?)

Feb 20 2017, 10:40 AM · research, Whonix, upstream, Whonix 14

Feb 17 2017

dau added a comment to T622: Run unMessage on Whonix.

unMessage is an anonymous communication program that uses Tor to hide metadata of participants. Its still in early development, however a major new feature such as Tor-to-Tor audio chat (the first such implementation we are aware of) has been included. Major additions like file-sharing support, video conferencing and a portable code-base mobile platforms are planned.

Our major goal is to provide a better UX and a competitive feature set to move users away from proprietary solutions that don't respect privacy. Though not ready for mass adoption yet, we encourage the more technical audience among you to go ahead try it out. We appreciate any feedback and/or pull requests.

Check us out on Github:

https://github.com/AnemoneLabs/unmessage

Feb 17 2017, 12:11 AM · Whonix

Feb 13 2017

dau added a comment to T622: Run unMessage on Whonix.

@dau The Tor Project is running a series of blog posts on OS's and programs that make use of their network as part of raising awareness about them in the community. These are short articles that describe what the respective projects are about and their future goals. I want to let them know about unMessage. This will get attention and potentially attract more coders. What do you think? Check with your friend rxcomm and let me know.

Feb 13 2017, 10:16 PM · Whonix

Feb 3 2017

dau added a comment to T622: Run unMessage on Whonix.

@dau That's awesome :) I was waiting for more competition in the Onion messaging space and I like that you guys are using an extra crypto layer as fallback.

Thanks for letting us know about it. I'll give it a spin and post feedback on Github.

Feb 3 2017, 7:00 AM · Whonix
dau added a comment to T622: Run unMessage on Whonix.
In T622#11988, @Patrick wrote:

Thank you for your interest! Don't worry too much about formalities. I like clean tickets and reorganize them if useful. Anyhow, this ticket is very much fine.

answered here:
https://github.com/AnemoneLabs/unmessage/issues/2#issuecomment-277091439

also created port to ephemeral Tor hidden services / python-stem:
https://github.com/AnemoneLabs/unmessage/issues/4

Feb 3 2017, 1:01 AM · Whonix

Feb 2 2017

dau created T622: Run unMessage on Whonix.
Feb 2 2017, 9:41 PM · Whonix

Aug 20 2016

dau added a comment to T367: Mixmaster GUI Options.
In T367#9898, @HulaHoop wrote:

As soon as TUF for python is packaged for Debian I will document how to install nymphemeral with it.

Background: TUF provides a secure updater framework that guarantees package and update integrity. It is now integrated in many alternative installer/updaters that traditionally had poor to no security. Using it with pip will give the same security benefits as if it was available under Debian's apt.

Aug 20 2016, 3:20 AM · user documentation, research, Whonix, usability

Feb 10 2016

dau added a comment to T367: Mixmaster GUI Options.
In T367#8102, @Patrick wrote:

I never read that a test suite is required for a package to be accepted
into Debian. Unfortunately, I don't know what the best more straight
forward guide into Debian packaging [of a python project] is.

whonix-setup-wizard is a python package maintained by Whonix.

https://github.com/Whonix/whonix-setup-wizard

It has only one dependency, genmkfile that is unfortunately not yet
packaged for Debian but hopefully sooner than later.

https://github.com/Whonix/genmkfile

You can see there the /debian sub folder. You could copy and paste it
as a template and then modify for nymphemeral.

https://github.com/Whonix/whonix-setup-wizard/tree/master/debian

Debian package build instructions are included in the project's readme.

https://github.com/Whonix/whonix-setup-wizard/blob/master/README.md

It produces a 100 % lintian (including --pedantic) warning free
package. [Lintian is the package quality checker by Debian.] And
reasonable absence of lintian warnings this is a condition for packages
to be accepted in Debian.

There surely are other ways to package python based software for Debian.
Look into a few python based software packages and download their
sources. (apt-get source pkg-name)

There is also the Debian mentors mailing list, which helps with
packaging questions.

https://lists.debian.org/debian-mentors/

I suggest to try to reach out to the Debian Anonymity Tools Team for help.

https://tracker.debian.org/teams/anonymity-tools/

Feb 10 2016, 8:48 PM · user documentation, research, Whonix, usability
dau added a comment to T367: Mixmaster GUI Options.
In T367#8079, @Patrick wrote:

What is the status of this ticket?

Feb 10 2016, 7:09 PM · user documentation, research, Whonix, usability

Aug 12 2015

dau added a comment to T374: Nymserver Documentation.

Thanks HulaHoop! That's very interesting.

Aug 12 2015, 5:55 PM · Whonix, user documentation

Aug 11 2015

dau added a comment to T374: Nymserver Documentation.
In T374#6341, @HulaHoop wrote:
  • Nymservers do support attachments. Any files attached in a conventional message are converted into base64 encoded text appended to the end of the message body:
Aug 11 2015, 4:37 AM · Whonix, user documentation

Jul 20 2015

dau added a comment to T367: Mixmaster GUI Options.

Hi HulaHoop!

Jul 20 2015, 7:47 PM · user documentation, research, Whonix, usability

Jul 18 2015

dau added a comment to T367: Mixmaster GUI Options.
In T367#5960, @HulaHoop wrote:

Safe defaults are always the smart thing to do, so I agree that the current behavior should be as it is out-of the box, but for more flexibility can you make direct access to the user keyring an option that powerusers can enable? To make sure no mistakes are made, Nymphemeral could show a confirmation prompt warning the user not to use the option unless they know what they're doing.

Upgrading Server Manager to handle this still works, I'm just putting ideas out there :)

Jul 18 2015, 1:39 AM · user documentation, research, Whonix, usability

Jul 17 2015

dau added a comment to T367: Mixmaster GUI Options.
In T367#5952, @HulaHoop wrote:

Awesome. I have Nymphemeral up and running.

Jul 17 2015, 1:34 AM · user documentation, research, Whonix, usability

Jul 16 2015

dau added a comment to T374: Nymserver Documentation.
In T374#5936, @HulaHoop wrote:

Thanks a lot Felipe, you've done a great job.

Jul 16 2015, 8:40 PM · Whonix, user documentation
dau added a comment to T367: Mixmaster GUI Options.

I can successfully upgrade nymphemeral with pip however I still have the same error with mix.cfg

Jul 16 2015, 8:21 PM · user documentation, research, Whonix, usability
dau added a comment to T367: Mixmaster GUI Options.
In T367#5937, @HulaHoop wrote:

I was using pip. Should I try building from source?

Jul 16 2015, 6:18 AM · user documentation, research, Whonix, usability

Jul 15 2015

dau added a comment to T367: Mixmaster GUI Options.

It seems that pip has been updated and nymphemeral is not installing as it should. HulaHoop, when you were testing nymphemeral, did you install it with pip or built it from source?

Jul 15 2015, 8:24 PM · user documentation, research, Whonix, usability
dau added a comment to T374: Nymserver Documentation.

I moved the Message Path into its own section above Instructions to give an overview. Do you think this is the right place?

Jul 15 2015, 2:56 PM · Whonix, user documentation

Jul 14 2015

dau added a comment to T374: Nymserver Documentation.
In T374#5925, @HulaHoop wrote:
Jul 14 2015, 9:53 PM · Whonix, user documentation
dau added a comment to T374: Nymserver Documentation.

Excellent. It was a better polished version of what I wrote. I replaced everything with your text. Feel free to directly edit the page and I'll accept the changes.

Jul 14 2015, 2:54 AM · Whonix, user documentation

Jul 13 2015

dau added a comment to T374: Nymserver Documentation.

Created new page at https://www.whonix.org/wiki/Nymservers

Ok I'll add the part about sending choices in the introduction, to give the user the whole idea of how it works.

Jul 13 2015, 7:55 AM · Whonix, user documentation

Jul 12 2015

dau added a comment to T374: Nymserver Documentation.
In T367#5918, @HulaHoop wrote:

I pushed a major change to the wiki. Many parts are rewritten and new information added.

Jul 12 2015, 8:40 PM · Whonix, user documentation
dau added a comment to T367: Mixmaster GUI Options.
In T367#5906, @HulaHoop wrote:

Thanks Felipe. I followed your directions and now it works!

Jul 12 2015, 2:33 AM · user documentation, research, Whonix, usability

Jul 11 2015

dau added a comment to T367: Mixmaster GUI Options.
In T367#5902, @HulaHoop wrote:

You know how users will have to renew remailer chain information - usually once a day? this dummy message sending test could be part of that procedure instead of something done on (every) startup by nymphemeral.

Jul 11 2015, 7:19 AM · user documentation, research, Whonix, usability

Jul 10 2015

dau added a comment to T367: Mixmaster GUI Options.

So are you just checking for the existence of the file or are you also parsing its contents and going off of that? The first method (if possible to implement) would make it more robust because it makes less assumptions I think.

Jul 10 2015, 9:11 PM · user documentation, research, Whonix, usability

Jul 4 2015

dau added a comment to T367: Mixmaster GUI Options.
In T367#5855, @HulaHoop wrote:

Got it. Are you still having the same mix.cfg error?

Yes. I've also tried many other likely paths but with no success unfortunately.

Jul 4 2015, 7:02 AM · user documentation, research, Whonix, usability
dau added a comment to T367: Mixmaster GUI Options.
In T367#5826, @Patrick wrote:
In T367#5805, @dau wrote:

I am not sure if I should be posting here. But apparently I am allowed to.

No worries. It's open to public. Anything constructive to this ticket. Your welcome here. Your post looks very constructive.

I assume Whonix already comes with Mixmaster installed, but probably somewhere else.

Yes. Current Whonix stuff, related to mixmaster:

Jul 4 2015, 12:41 AM · user documentation, research, Whonix, usability

Jul 2 2015

dau added a comment to T367: Mixmaster GUI Options.

I am not sure if I should be posting here. But apparently I am allowed to.

Jul 2 2015, 9:13 PM · user documentation, research, Whonix, usability