.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-http://www.debian.org/
___
tor-dev mailing list
tor-dev@lists.torproject.org
https
to this? Something different?
Cheers,
weasel
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-http://www.debian.org
On Sat, 06 Apr 2013, Andrew Lewman wrote:
On Fri, 5 Apr 2013 15:53:57 +0200
Peter Palfrader wea...@torproject.org wrote:
Tom asked what was needed to get our website moved to git.
Probably not much. And while we're at it we could split the
repository into two parts:
- things
301s to /obfsproxy.git and to
/pluggable-transports/pyobfsproxy.git .
Done the first two as discussed on IRC.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
it.
[Also, tor-dev is not a place for such discussions. I wished we had a
project list, but alas. If somebody finds a proper place to have such a
discussion, please Cc me.]
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http
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
FINGERPRINT NL
Why not implictly revoke any previous signing key when we see a new,
valid signing key certificate with a later published timestamp?
It would appear to be simpler and require less state.
Cheers,
--
| .''`. ** Debian **
Peter Palfrader
On Sun, 11 Jan 2015, Nick Mathewson wrote:
On Sun, Jan 11, 2015 at 4:23 AM, Peter Palfrader wea...@torproject.org
wrote:
On Sat, 10 Jan 2015, Nick Mathewson wrote:
This proposal describes a simple way for directory authorities to
perform signing key revocation.
2
https://www.palfrader.org/volatile/2015-04-17-VjBkc8DWV8c/list
Discuss :)
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-http
the list be treated similar to the geoip database we
ship at tor. Before release, it gets updated in git and then is part of
the source.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org
be https://spec.torproject.org/tor-spec or
something like that? I'm less convinced it needs a document served
there, and I don't think it should live on www.tpo or plain tpo.
Cheers,
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
**
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-http://www.debian.org/
___
tor-dev mailing list
tor-dev@lists.torproject.org
https
/tor.service and the systemd.exec(5) manpage.
You can override these by making your own
/etc/systemd/system/tor.service file.
Cheers,
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating
fix this? Or what the best
workaround would be to document?
Thanks,
weasel
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https
git config --global --add fetch.fsckobjects true
git config --global --add receive.fsckobjects true
might also work. (However, I haven't verified it.)
Cheers,
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
Hi!
On Thu, 24 Mar 2016, Hugo Maxwell Connery wrote:
> PS: Sorry, this may be completely outside of the normal
> channel of this space.
We are trying to keep this list focused on Tor development.
Please do not post off-topic content.
Thank you.
___
René Mayrhofer schrieb am Montag, dem 19. September 2016:
> Update: After a hint by Peter Palfrader, I now set the Address option as
> well:
>
> root@tor2 ~ # grep Address /etc/tor/torrc
> Address 193.171.202.146
> OutboundBindAddress 193.171.202.150
>
> This seems to wo
On Tue, 03 Jul 2018, Peter Palfrader wrote:
> On Sun, 01 Jul 2018, Iain Learmonth wrote:
>
> > Hi,
> >
> > On 30/06/18 15:42, nusenu wrote:
> > > but maybe someone else would be willing to invoke a
> > > "ln" commands everytime a new new alph
0.3.4.x-jessie
>
> As an alternative strategy, symbolic links for old alpha repositories
> point to the current stable repository.
apt will complain if the Suite/Codename in the Release file doesn't
match what it expects. symlinks don't change anything.
--
On Tue, 03 Jul 2018, teor wrote:
> Maybe there is no good solution to this problem.
> What’s the least worse solution?
Stop shipping alpha versions where people can find them easily?
--
| .''`. ** Debian **
Peter Pal
On Sun, 07 Oct 2018, nusenu wrote:
> Hi,
>
> the tor 0.3.5.x repos (example [1]) exist since some time
> but are empty since then, is that intentional?
All existing 0.3.5.x releases fail to build from source (#27781).
--
| .''`. ** Debian **
t be a (2).
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `-https://www.debian.org/
___
tor-dev mailing lis
22 matches
Mail list logo
