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. Maybe also publish in a DNS TXT record or something?
On Jan 5, 2018 00:48, "Andreas Krey" a.krey@gmx.de wrote:
Hi everybody,
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?
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.
- Andreas
-- "Totally trivial. Famous last words." From: Linus Torvalds <torvalds@*.org> Date: Fri, 22 Jan 2010 07:29:21 -0800 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
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@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:
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@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:
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 ------------------------------------------------------------------------
(Earlier reply has somehow vanished...)
On Mon, 08 Jan 2018 00:49:16 +0000, teor wrote: ...
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.
The newest/highest, probably. Essentially the one also proclaimed as stable on the source download page.
Should stable be 0.3.1 (and change to 0.3.2 next week)?
Yes.
Do you want a long-term support branch as well?
No. I just need one version to build a relay.
...
If you want something that's easier to scrape, and signed, check for new source releases at:
Scraping would be a fallback.
...
$ 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
Basically current would be the highest non-rc on the list, and alpha would be the -rc (or current if no -rc present).
Andreas
Would any of you know the setup for dd-wrt the onion router project under the services Tab
On January 12, 2018 4:07:27 PM EST, Andreas Krey a.krey@gmx.de wrote:
(Earlier reply has somehow vanished...)
On Mon, 08 Jan 2018 00:49:16 +0000, teor wrote: ...
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.
The newest/highest, probably. Essentially the one also proclaimed as stable on the source download page.
Should stable be 0.3.1 (and change to 0.3.2 next week)?
Yes.
Do you want a long-term support branch as well?
No. I just need one version to build a relay.
...
If you want something that's easier to scrape, and signed, check for new source releases at:
Scraping would be a fallback.
...
$ 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
Basically current would be the highest non-rc on the list, and alpha would be the -rc (or current if no -rc present).
Andreas
-- "Totally trivial. Famous last words." From: Linus Torvalds <torvalds@*.org> Date: Fri, 22 Jan 2010 07:29:21 -0800 _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi,
Please start a new thread for new questions.
On 13 Jan 2018, at 08:49, Grander Marizan gmarizan@gmx.com wrote:
Would any of you know the setup for dd-wrt the onion router project under the services Tab
I've never set this up myself, but I just did a search online:
How to setup OpenVPN on DD-WRT using TorGuard Startup Script https://torguard.net/knowledgebase.php?action=displayarticle&id=47
T
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
On 13 Jan 2018, at 08:07, Andreas Krey a.krey@gmx.de wrote:
(Earlier reply has somehow vanished...)
On Mon, 08 Jan 2018 00:49:16 +0000, teor wrote: ... 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.
The newest/highest, probably. Essentially the one also proclaimed as stable on the source download page.
Should stable be 0.3.1 (and change to 0.3.2 next week)?
Yes.
Do you want a long-term support branch as well?
No. I just need one version to build a relay.
...
If you want something that's easier to scrape, and signed, check for new source releases at:
Scraping would be a fallback.
...
$ 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
Basically current would be the highest non-rc on the list, and alpha would be the -rc (or current if no -rc present).
We also tag releases with "alpha", so these should be included in the alpha branch as well.
Is there any reason you can't use the source tarballs for this? They are signed, unlike git branches.
T
tor-relays@lists.torproject.org
-
Andreas Krey -
Chad MILLER -
Grander Marizan -
teor