[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #12547 [BridgeDB]: Get analysed data from bridge reachability tests to tor-devs
#12547: Get analysed data from bridge reachability tests to tor-devs
--------------------------+---------------------------------------
Reporter: hellais | Owner: sysrqb
Type: task | Status: new
Priority: normal | Milestone:
Component: BridgeDB | Version:
Resolution: | Keywords: ooni, bridge-reachability
Actual Points: | Parent ID: #12544
Points: |
--------------------------+---------------------------------------
Comment (by hellais):
Replying to [comment:1 isis]:
> Correct me if I'm wrong, but I think we've all decided that (for now at
least) OONI people will be running the collector mentioned in #12545,
which means that this access-controlled web interface would also be on
that machine rather than BridgeDB.
>
Yes that is correct. I replied also on that ticket, thanks for raising the
question.
> Does the OONI collector already have a builtin web interface like this?
If so, does it come with its own access control mechanisms, or would it
need to be run behind e.g. Apache?
Currently the collector does not do any publishing of the collected
reports, it just writes them to a directory that then needs some logic to
expose them for use by, for example, the BridgeDB team.
I have set everything up so that it all runs inside of isolated Docker
containers so this would be a mater of setting up another docker container
that exposes the directory where the reports are written to in some way. I
think running an apache or nginx is indeed the simplest solution. If we
decide that we need something a bit more complicated we can also write an
ad-hoc web application, but for the moment I would keep it as simple as
possible.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12547#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs