Re: [tor-dev] Symlink to latest sources
Dear Roger, You've avoided that for both binaries and sources? That's interesting. I guess it makes sense, if it's been a problem before. I mostly would like to be able to wget the the sources and build them automatically, without having to specify a version number. Whenever I setup a new machine, I like to make it a tor relay; I don't particularly care about versions, just as long as it's new enough to not have any old vulnerabilities. Best, Peter
Hi Peter,
So far we have avoided doing this approach, since it increases the number of user support cases where we ask "what version?" and they say "latest" because their file name doesn't actually tell them what version it is.
I guess we could try adding the symlink but then never tell anybody about it, in hopes that users will keep downloading the files that have version numbers in their names.
What problem are you trying to solve?
--Roger
On Tue, Sep 09, 2014 at 04:35:15PM -0400, Peter Swire wrote:
Dear Roger,
You've avoided that for both binaries and sources? That's interesting. I guess it makes sense, if it's been a problem before.
I mostly would like to be able to wget the the sources and build them automatically, without having to specify a version number. Whenever I setup a new machine, I like to make it a tor relay; I don't particularly care about versions, just as long as it's new enough to not have any old vulnerabilities.
I suppose fetching tor-latest.tgz could 302 redirect to tor-0.2.x.y.tgz? Then wget would retrieve it with the version number, addressing the support issue? - Ian
On Tue, 09 Sep 2014, Ian Goldberg wrote:
On Tue, Sep 09, 2014 at 04:35:15PM -0400, Peter Swire wrote:
You've avoided that for both binaries and sources? That's interesting. I guess it makes sense, if it's been a problem before.
I mostly would like to be able to wget the the sources and build them automatically, without having to specify a version number. Whenever I setup a new machine, I like to make it a tor relay; I don't particularly care about versions, just as long as it's new enough to not have any old vulnerabilities.
I suppose fetching tor-latest.tgz could 302 redirect to tor-0.2.x.y.tgz? Then wget would retrieve it with the version number, addressing the support issue?
wget wouln't, unless you pass it --trust-server-names, which is a bad idea. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `- http://www.debian.org/
On Wed, Sep 10, 2014 at 08:31:56AM +0200, Peter Palfrader wrote:
On Tue, 09 Sep 2014, Ian Goldberg wrote:
On Tue, Sep 09, 2014 at 04:35:15PM -0400, Peter Swire wrote:
You've avoided that for both binaries and sources? That's interesting. I guess it makes sense, if it's been a problem before.
I mostly would like to be able to wget the the sources and build them automatically, without having to specify a version number. Whenever I setup a new machine, I like to make it a tor relay; I don't particularly care about versions, just as long as it's new enough to not have any old vulnerabilities.
I suppose fetching tor-latest.tgz could 302 redirect to tor-0.2.x.y.tgz? Then wget would retrieve it with the version number, addressing the support issue?
wget wouln't, unless you pass it --trust-server-names, which is a bad idea.
Oops, you're right, of course. Good call. -- Ian Goldberg Associate Professor and University Research Chair Cheriton School of Computer Science, University of Waterloo Visiting Fellow, Clare Hall, University of Cambridge
On Tue, Sep 9, 2014 at 4:35 PM, Peter Swire <swirepe@gmail.com> wrote:
automatically, without having to specify a version number. Whenever I setup a new machine, I like to make it a tor relay; I don't particularly care about versions, just as long as it's new enough to not have any old vulnerabilities.
A script using features of git to determine and pull whatever latest branch or release tag is laid down or followed is possible.
participants (4)
-
grarpamp -
Ian Goldberg -
Peter Palfrader -
Peter Swire