Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

created a data policy for OONI #57

Merged
merged 5 commits into from
May 13, 2016
Merged

created a data policy for OONI #57

merged 5 commits into from
May 13, 2016

Conversation

agrabeli
Copy link
Member

@agrabeli agrabeli commented May 5, 2016

I wrote a Data Policy for OONI. All feedback welcome. :)


OONI software users can choose to *opt-out* from the collection of country codes
by editing the ooniprobe configuration file inside of
`~/.ooni/ooniprobe.conf`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps it would be good to point to a piece of documentation where it is explained how to do so? My initial suggestion was to provide such information inline, except that linking is more robust in the long term to updates in the config file syntax.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. I added a link to the configuration section of the ooniprobe README. Currently this documentation is not comprehensive, but I imagine that it will get updated soon and the link here will point to that,

@bassosimone
Copy link
Contributor

I really like what I've read, well done! I've added some comments in specific places where I think it would make sense to invest some more effort to improve the text!


OONI does *not* use tracking cookies, analytics or any other tracking
technologies through its [website](https://ooni.torproject.org/) and does *not*
collect any information about its website visitors.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should ensure that no web server logs are being kept.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI, this is the log configuration for ooni.tpo: LogFormat "0.0.0.1 - %u %{[%d/%b/%Y:00:00:00 %z]}t \"%r\" %>s %b \"%{Referer}i\" \"-\" %{Age}o"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! @hellais just checked this and I'm editing the document now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hellais does this applies to both access and error HTTP logs?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For measurements.ooni.torproject.org and explorer.ooni.torproject.org :
Error log: /dev/null
Access log:

ap $remote_addr $anon_remote_addr {
          "~^(?<ip_a>\d+\.\d+)\.\d+\.\d+" "$ip_a";
        }
        log_format combined_anon '$anon_remote_addr.0.0 - $remote_user [$time_local] '
                                 '"$request" $status $body_bytes_sent '
                                 '"$http_referer" "$http_user_agent"';

@hellais are there more servers that we don't cover?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anadahz I was told the error log may include more information for ooni.torproject.org, though it wasn't specified exactly what that could be.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hum, maybe we should not be logging the http_user_agent and the first 2 octets of the IP.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hellais any suggestions where to find more info about the error log info of ooni.torproject.org does this collect the same info as in www.torproject.org?

Access.log suggestion:

log_format combined_anon '0.0.0.9 - $remote_user [$time_local] '
                                 '"$request" $status $body_bytes_sent '
                                 '"$http_referer"';

@anadahz
Copy link
Contributor

anadahz commented May 5, 2016

It seems that there is a lot of text duplication, perhaps it will make sense to have
a section with the same text for all affected subsections that share the same
text.
It will be beneficial to add some ooni-spec wiki pages relevant to the
data policy.

Overall really good work thank you for working on this!

@bassosimone
Copy link
Contributor

bassosimone commented May 7, 2016

It seems that there is a lot of text duplication [...]

Yes, I noticed the same and was about to make a similar remarks. Then, I though that perhaps, since this document is meant to be read more by users than by developers, some redundancy inside it would have been beneficial to the reader.

@bassosimone bassosimone mentioned this pull request May 7, 2016
OONI software users can choose to *opt-out* from the collection of their
network's ASN by [editing the ooniprobe
configuration](https://github.com/TheTorProject/ooni-probe#configuring-
ooniprobe) file inside of `~/.ooni/ooniprobe.conf`.
Copy link
Member

@hellais hellais May 7, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to self. Fix the link in the merge.

@hellais
Copy link
Member

hellais commented May 7, 2016

Yeah I think it's ok that there is duplication as I would expect that somebody would read this not necessarily entirely, but just the specific sections they are interested in.
As such I think it's good to have things re-iterated in all relevant sections.

As soon as the following issues:

are resolved I will proceed in merging this.

@hellais
Copy link
Member

hellais commented May 8, 2016

This looks good to me. I think it's good to merge.

@hellais
Copy link
Member

hellais commented May 13, 2016

I think this is ready to merge. Will cleanup the broken links and integrate into master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants