GSoC 17 | Name System API for Tor Onion Services
Hi, I am Ivan Tham. Currently studying in Computer Science in APIIT Malaysia. I am interested particapate in Google Summer of Code 2017 under tor organization. I am interested to see Proposal 224 coming along but I would really like to see [Proposal 272][0] and hope that tor hidden services can be more user-friendly. What do you think of the projects? Is the proposal too immature? I had looked into [OnioNS][1] as well and like the idea of having different types of DNS records for tor hidden services, how does it integrate with [Proposal 272][0]? [0]: https://lists.torproject.org/pipermail/tor-dev/2016-October/011524.html [1]: https://lists.torproject.org/pipermail/tor-dev/2015-May/008826.html
Pickfire <pickfire@riseup.net> writes:
Hi,
I am Ivan Tham. Currently studying in Computer Science in APIIT Malaysia. I am interested particapate in Google Summer of Code 2017 under tor organization. I am interested to see Proposal 224 coming along but I would really like to see [Proposal 272][0] and hope that tor hidden services can be more user-friendly.
Hello, there is still interest in this proposal but unfortunately it hasn't been revised since it was first posted on the mailing list. The mailing list feedback unfortunately has not been incorporated to the proposal yet; particularly the comments by David Fifield are very relevant and should be considered carefully before taking the proposal too seriously. In general, I suggest to anyone who wants to work on this proposal, to do it using a Tor controller instead of hacking the main C tor code. meejah suggested this here: https://lists.torproject.org/pipermail/tor-dev/2016-October/011517.html and it seems like a proper solution here would involve controller events like NEWRESOLVE, MAPADDRESS, and plus some extra magic. I must say that this project is definitely relevant for GSoC, but it needs a _strong_ and _independent_ student that can handle it. Also, Tor is currently having a real life meeting so most of us are very busy. We plan to discuss the proposal during the meeting, so I hope to send a short update next week at some point if I find the time (and also merge it to torspec.git since it's currently missing). I'm looking forward to any proposal comments, as well as responses to the feedback received. Also, if someone can sketch an implementation plan for the controller idea that would be great. Sorry for the uncertainties here and good luck! Cheers!
George Kadianakis <desnacked@riseup.net> wrote:
Pickfire <pickfire@riseup.net> writes:
I am Ivan Tham. Currently studying in Computer Science in APIIT Malaysia. I am interested particapate in Google Summer of Code 2017 under tor organization. I am interested to see Proposal 224 coming along but I would really like to see [Proposal 272][0] and hope that tor hidden services can be more user-friendly.
there is still interest in this proposal but unfortunately it hasn't been revised since it was first posted on the mailing list. The mailing list feedback unfortunately has not been incorporated to the proposal yet; particularly the comments by David Fifield are very relevant and should be considered carefully before taking the proposal too seriously.
Does
In general, I suggest to anyone who wants to work on this proposal, to do it using a Tor controller instead of hacking the main C tor code. meejah suggested this here: https://lists.torproject.org/pipermail/tor-dev/2016-October/011517.html
Does that mean that I well be working on the prototype with python first and then convert it into C?
and it seems like a proper solution here would involve controller events like NEWRESOLVE, MAPADDRESS, and plus some extra magic.
I don't quite understand what does that mean.
I must say that this project is definitely relevant for GSoC, but it needs a _strong_ and _independent_ student that can handle it.
I will definitely do my best for it but I will really need a mentor to help because I am confused by some parts of it as well.
Also, Tor is currently having a real life meeting so most of us are very busy. We plan to discuss the proposal during the meeting, so I hope to send a short update next week at some point if I find the time (and also merge it to torspec.git since it's currently missing).
Nice, can I join as well to have a clearer understanding of it?
I'm looking forward to any proposal comments, as well as responses to the feedback received. Also, if someone can sketch an implementation plan for the controller idea that would be great.
Sorry for the uncertainties here and good luck! Cheers!
No problem, I still see that the proprosal isn't very solid right now.
Ivan Tham <pickfire@riseup.net> writes:
George Kadianakis <desnacked@riseup.net> wrote:
Pickfire <pickfire@riseup.net> writes:
I am Ivan Tham. Currently studying in Computer Science in APIIT Malaysia. I am interested particapate in Google Summer of Code 2017 under tor organization. I am interested to see Proposal 224 coming along but I would really like to see [Proposal 272][0] and hope that tor hidden services can be more user-friendly.
there is still interest in this proposal but unfortunately it hasn't been revised since it was first posted on the mailing list. The mailing list feedback unfortunately has not been incorporated to the proposal yet; particularly the comments by David Fifield are very relevant and should be considered carefully before taking the proposal too seriously.
Does
In general, I suggest to anyone who wants to work on this proposal, to do it using a Tor controller instead of hacking the main C tor code. meejah suggested this here: https://lists.torproject.org/pipermail/tor-dev/2016-October/011517.html
Does that mean that I well be working on the prototype with python first and then convert it into C?
Hello, I think a well made controller-based prototype in Python and one or two PoC integrations of simple name systems (e.g. local hosts file, remote hosts file) should be fine for a GSoC summer project. If we like the controller prototype we could consider writing it in C in the future.
and it seems like a proper solution here would involve controller events like NEWRESOLVE, MAPADDRESS, and plus some extra magic.
I don't quite understand what does that mean.
Please check control-spec.txt for a description of those events: https://gitweb.torproject.org/torspec.git/tree/control-spec.txt It might make things clearer.
I must say that this project is definitely relevant for GSoC, but it needs a _strong_ and _independent_ student that can handle it.
I will definitely do my best for it but I will really need a mentor to help because I am confused by some parts of it as well.
Hmm. Which parts did you find confusing? Cheers!
George Kadianakis <desnacked@riseup.net> writes:
Pickfire <pickfire@riseup.net> writes:
Hi,
I am Ivan Tham. Currently studying in Computer Science in APIIT Malaysia. I am interested particapate in Google Summer of Code 2017 under tor organization. I am interested to see Proposal 224 coming along but I would really like to see [Proposal 272][0] and hope that tor hidden services can be more user-friendly.
Hello,
there is still interest in this proposal but unfortunately it hasn't been revised since it was first posted on the mailing list. The mailing list feedback unfortunately has not been incorporated to the proposal yet; particularly the comments by David Fifield are very relevant and should be considered carefully before taking the proposal too seriously.
In general, I suggest to anyone who wants to work on this proposal, to do it using a Tor controller instead of hacking the main C tor code. meejah suggested this here: https://lists.torproject.org/pipermail/tor-dev/2016-October/011517.html and it seems like a proper solution here would involve controller events like NEWRESOLVE, MAPADDRESS, and plus some extra magic.
I must say that this project is definitely relevant for GSoC, but it needs a _strong_ and _independent_ student that can handle it.
Also, Tor is currently having a real life meeting so most of us are very busy. We plan to discuss the proposal during the meeting, so I hope to send a short update next week at some point if I find the time (and also merge it to torspec.git since it's currently missing).
FWIW, I merged the draft proposal from [tor-dev] to torspec, so that we have a common point of reference. The proposal still needs improvements before we can call it complete. You can find it as proposal279: https://gitweb.torproject.org/torspec.git/tree/proposals/279-naming-layer-ap... Cheers!
On 03/21/2017 10:54 AM, Pickfire wrote:
I am Ivan Tham. Currently studying in Computer Science in APIIT Malaysia. I am interested particapate in Google Summer of Code 2017 under tor organization. I am interested to see Proposal 224 coming along but I would really like to see [Proposal 272][0] and hope that tor hidden services can be more user-friendly.
What do you think of the projects? Is the proposal too immature? I had looked into [OnioNS][1] as well and like the idea of having different types of DNS records for tor hidden services, how does it integrate with [Proposal 272][0]?
[0]: https://lists.torproject.org/pipermail/tor-dev/2016-October/011524.html [1]: https://lists.torproject.org/pipermail/tor-dev/2015-May/008826.html
Hi Ivan, I am the author and the main developer behind the Onion Name System (OnioNS) project, which I see you referenced above. You may be interested in reading my paper here: [0]. Development is on Github and I think that I have a very solid codebase, but I haven't commit anything recently as I've been busy with a full-time job as a pen tester and various other side projects that have occupied my time. In my mind, there are a couple of issues that impact naming systems: 1) The SHAttered attack against SHA-1. This certainly affects current onion services, and I'm personally a hesitant to enhance them with a naming system, since a SHA-1 collision would undermine the security of any naming system. 2) Prop224 is in the works and is still being finalized. Since the addresses are much larger, we certainly want to have a good naming system by the time it's ready to go, as this also encourages the transition to the new system. The naming system API ties into this. I would be very happy if you were to help implement the naming system API. It's currently possible to redirect the streams by sending commands to the tor control port, but an API would be much cleaner. [0]: https://www.degruyter.com/downloadpdf/j/popets.2017.2017.issue-1/popets-2017... -- Jesse
participants (4)
-
George Kadianakis -
Ivan Tham -
Jesse V -
Pickfire