- tor-dev - lists.torproject.org

small fixes for the sources.list generator (and new options)
by nusenu 03 Feb '18

03 Feb '18

Hi, since the tor relay guide depends on that page and it has a few issues I made some small fixes to it: https://www.torproject.org/docs/debian.html.en Bug 25107: sources.list generator: remove yakkety (we do not offer packages for it) Bug 25107: sources.list generator: add Ubuntu Artful Aardvark (17.10) Bug 25107: sources.list generator: remove zesty (we do not offer packages for it) Bug 25107: sources.list generator: add nightly-master option Bug 24994: point to the actual content describing alpha/stable differences Bug 25107: sources.list generator: update tor alpha version to 0.3.3.x Bug 25107: Update the tor alpha version (noscript page version) Bug 25107: fix sources.list generator for Debian Buster If someone with commit privileges has time to review and merge before the weekend that would be great. https://github.com/nusenu/torproject-webwml/tree/debian_sources.list_genera… Note: I did not care about the "(from source)" option. -- https://mastodon.social/@nusenu twitter: @nusenu_

2 3

stem support for v3 ephemeral onion services
by Micah Lee 01 Feb '18

01 Feb '18

Now that Tor Browser 7.5 is released and includes the tor 0.3.2 series, which supports next generation onion services, I would love to make OnionShare use these by default. Here is the issue [1]. OnionShare is written in python3 and relies on stem to communicate with the Tor controller. Although tor now supports v3 ephemeral onion services, stem still doesn't. Just take make sure, here's a quick test, with Tor Browser 7.5 (providing tor 0.3.2.9) open in the background, and using stem 1.6.0: == from stem.control import Controller c = Controller.from_port(port=9151) c.authenticate() tor_version = c.get_version().version_str print("Tor version: {}".format(tor_version)) print("Creating ephemeral onion service") res = c.create_ephemeral_hidden_service({ 80: 8080 }, await_publication=True, key_type='NEW', key_content='BEST') print("{}.onion".format(res.service_id)) == When executed, it still creates a v2 onion address: (env) user@dev ~/tmp $ python3 onionv3.py Tor version: 0.3.2.9 Creating ephemeral onion service wrvsjo4nlww3edsi.onion Right now OnionShare is blocked by stem supporting v3 onions. Does anyone know when we can expect support for this? [1] https://github.com/micahflee/onionshare/issues/461

4 5

Starting with contributing to Anonymous Local Count Statistics.
by Aruna Maurya 31 Jan '18

31 Jan '18

Hey! I was going through the Tor Volunteer page and came across the Anonymous local count statistics project. As a student it would be a great starting point and an even bigger opportunity to get a chance to collaborate and learn in the process. I would like to contribute to it, and would love to start as soon as possible. It would be great if someone could guide me through. Thanks for your time!! -- Regards, Aruna Maurya, CSE,B.tech, Blog <https://themindreserves.wordpress.com/> | Medium <https://medium.com/@arunamaurya>

2 1

website patches for new Tor relay guide sidenav entry
by nusenu 30 Jan '18

30 Jan '18

Hi Silvia, I submitted a (trivial) patch (in #24881) to add links to the new tor relay guide on the website and to remove previous guides that have been merged into the new guide. I noticed that since than new commits have been merged and these patches will probably no longer apply cleanly. I will try to ensure they apply (rebase) shortly before you have time to look at them if you can tell me approximately when that will be. thanks, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

2 2

non-anonymous ephemeral onion services with stem
by Micah Lee 30 Jan '18

30 Jan '18

The stem documentation for create_ephemeral_hidden_service [1] says: "Changed in version 1.5.0: Added support for non-anonymous services." But I can't figure out to actually use this feature. There doesn't seem to be a new argument to say if you want your onion service to be non-anonymous. It also says, "Changed in version 1.5.0: Added the basic_auth argument." But there's a new basic_auth argument you can pass into the function to use that. [1] https://stem.torproject.org/api/control.html#stem.control.Controller.create…

5 12

trac component for check.tpo?
by nusenu 27 Jan '18

27 Jan '18

what is the correct trac component to report that check.tpo is down? Webpages/Website? http://downforeveryoneorjustme.com/check.torproject.org -- https://mastodon.social/@nusenu twitter: @nusenu_

2 1

Re: [tor-dev] Marker branch for current tor release(s)
by teor 25 Jan '18

25 Jan '18

Hi, Tor branches are a question for tor-dev@, I am directing all responses there. Also, I fixed the top-post. > On Jan 5, 2018 00:48, "Andreas Krey" <a.krey(a)gmx.de> wrote: > > https://www.torproject.org/download/download.html.en in the source code 'tab' > states the current stable and alpha version of tor. > > Would it be possible to publish the current states as branches 'stable' and > 'alpha' (or 'testing', or 'unstable') in the git repo? What do you mean by "alpha" and "stable" ? When tor 0.3.2.9 is released next week, there will be no alpha version. When this happens, do you want master, or the latest stable? When there are multiple supported tor versions, which one should be stable? At the moment, we support 0.2.5 and 0.2.9 as long-term support, and 0.3.0 and 0.3.1 as regular releases. Should stable be 0.3.1 (and change to 0.3.2 next week)? Do you want a long-term support branch as well? Should it be 0.2.5 or 0.2.9? > That would help us tor-from-source builders to just fetch the repo, and > if the respective branch changes, to rebuild and redeploy. Looking for a > new release tag or screen-scraping said web page is a bit hairy, and feels > unnecessary. If you want something that's easier to scrape, and signed, check for new source releases at: https://dist.torproject.org/ We provide the latest Tor Browser version through a URL (which I can't remember right now). Maybe we could do the same thing with Tor. > On 5 Jan 2018, at 23:17, Chad MILLER <chad(a)cornsilk.net> wrote: > > I second this. > > There's a recommended-versions list in the consensus, but you have to already have Tor available and running to get it. No, you don't need Tor: $ curl http://197.231.221.211:9030/tor/status-vote/current/consensus-microdesc | grep server-versions | tr "," "\n" | tail -1 0.3.2.8-rc Or you can do this far more reliably in Python using stem: https://stem.torproject.org/ > Maybe also publish in a DNS TXT record or something? Is that secure? Can you sign a TXT record? T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------

4 7

Pluggable transports research
by Jodi Spacek 25 Jan '18

25 Jan '18

I'm a master's student at the University of British Columbia (Vancouver, Canada) where I'm primarily researching anonymous systems and censorship. I would be delighted to contribute to pluggable transports. Of particular interest is image and audio data stenography - is anything is in the works for this or is it outdated? My aim is to add this functionality while fully testing and evaluating it as part of my thesis project. I refer to the list of idea suggestions here: https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/ideas Any guidance is greatly appreciated. Thanks so much! Jodi p.s.: Please advise if this is not the correct mailing list. and perhaps belongs in tor-assistants. If so, I will inquire there once my access is (hopefully!) granted. -- www.jodispacek.com

5 5

tor failing to resolve some dns records
by blaze glory 23 Jan '18

23 Jan '18

3 2

WIP proposal for migration to TLS 1.3
by isis agora lovecruft 23 Jan '18

23 Jan '18

Hello, It's not done yet; it probably has errors; it definitely has omissions; it's still riddled with "XXX"s everywhere… but here's a work-in-progress draft proposal for migrating our link protocol(s) to use TLS 1.3: https://gitweb.torproject.org/user/isis/torspec.git/log/?h=tls13 It's not quite ready for a whole bunch of feedback yet, since I'm still reading through all the specs and writing the proposal. However, if you're super knowledgeable about TLS 1.3 and have opinions or ideas or see a mistake/misunderstanding somewhere, please feel free to share! Thanks! Best regards, -- ♥Ⓐ isis agora lovecruft _________________________________________________________ OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35 Current Keys: https://fyb.patternsinthevoid.net/isis.txt

1 0