> On 18. Jan 2021, at 18:00, Roger Dingledine wrote:
> While I was looking at moria1's directory activity during the overload,
> I did say to myself "wow that's a lot of microdescriptor downloads".
>
> So hearing that torpy isn't caching mirodescriptors yet makes me think
> that it's a good bet
Hi James,
thanks for already working on patches for these issues! I will reply
inline some more.
> On 15. Jan 2021, at 23:56, James wrote:
>
> First of all, sorry if torpy hurt in some way Tor Network. It was
> unintentionally.
I believe you :)
> In any case, it seems to me that if there was
> On 11. Jan 2021, at 23:20, James wrote:
>
> Good day.
>
> Is there any chance that torpy (https://github.com/torpyorg/torpy) was
> triggered this issue
> https://gitlab.torproject.org/tpo/core/tor/-/issues/33018 ?
>
> Some wary facts:
> - Torpy using old fashion consensus (not mircodesc)
Hi Damian,
> On 2. Aug 2020, at 00:04, Damian Johnson wrote:
>
>> I'd like to use "ed25519 identity" or even just "identity" here going
>> forward.
>
> Gotcha. The name of 'identity' makes me wonder how this relates to
> relay fingerprints, which are the canonical identifier we use.
>
> Regardles
Hi there,
> On 19. May 2020, at 19:55, Nick Mathewson wrote:
> If we do decide to finally deprecate v2 onion services, that would be
> a significant maintenance burden reduced for us, but we'd have to
> handle the transition carefully. Unlike all the other migrations
> we've done, there isn't a
> On 24. Mar 2018, at 13:50, Rob Jansen wrote:
>> I think moria1 runs its own, and Faravahar runs its own. I've lost track
>> of the others, but I'd guess that bastet also runs its own, and that
>> maatuska pulls numbers from a bwauth that tjr runs.
>>
>> https://consensus-health.torproject.org/
Dear all,
below mail was meant to make it to tor-dev, but I got a bounce and didn't
notice until now. Whoops, my apologies.
> On 8. Dec 2016, at 14:29, Sebastian Hahn wrote:
>
> Hi,
>
>> On 08 Dec 2016, at 14:03, nusenu wrote:
>>
>> Dear tor directory
Hi there tor-dev,
as an update to those who didn't have the chance to meet with us in
Amsterdam or those who haven't followed the efforts to rely on C less,
here's what happened at the "let's not fight about Go versus Rust, but
talk about how to migrate Tor to a safer language" session and what
ha
> On 08 Dec 2016, at 15:02, nusenu wrote:
>> If we did this, also why would we blacklist the nonexit relays? That
>> seems to not make sense, as a relay operator could have multiple relays
>> that act as guard and exit simultaneously.
>
> Exit relays with the guard flag have usually a guard prob
Hi there,
Karsten and I have been working on metrics-related tasks and one thing
that's got a potential to cause us pain going forward is that of
"p"-lines in consensuses. Tor has added them with consensus method 5 but
only declared them to be optional. In practice, every consensus ever
produced t
Hey,
I've been wondering about the private_nets const in src/or/policies. It
was added in a96c0affcb4cda1a2e0d83d123993d10efc6e396 but Nick doesn't
remember why, and I'm hoping someone has an idea (maybe teor, who I've
CCed here, who documented this in a later commit?). If nobody knows why
we do t
Hi list,
I recently played with the Kitsune[0] framework to figure out whether we
might be able to use it to dynamically update (that is, perform an
update without restarting the process) Tor relays on Linux. This post is
just to make you aware such a thing has been attempted. I deem it
currently
Hi,
comments inline.
On 09/30/2015 12:01 PM, Nick Mathewson wrote:
Early versions of Tor checked the recommended-versions field in the
directory to see whether they should keep running. If they didn't
recognize
you did the thing where you
To override this, a Tor instance m
> On 11 Sep 2015, at 07:04, ilv wrote:
>> Next up is more of the same, especially focusing on website tickets
>> and preparing the community team's dev meeting contributions.
>
> Maybe we could have a session at the dev meeting to talk about the
> website (content, structure, translations, etc.)
> On 13 Aug 2015, at 18:50, Nick Mathewson wrote:
>
> On Wed, Aug 12, 2015 at 5:34 PM, nusenu wrote:
>> from today's measurement meeting:
>>
>>> 15:00:20 karsten: I've decided I'm going to fix the definition of
>>> median
>>> 15:00:26 in the tor sourcecode
>>> 15:00:36 virgil: is it broken
Hi!
> On 20 Mar 2015, at 16:55, Nick Mathewson wrote:
>
> IDEAS
> =
Many great ideas! Here's a few more, mostly just adding a bit to the
things you already listed. Some of them make me kind of uneasy because
they really are testing only and could be used for much unhappiness on
the real net
Hi teor,
> On 22 Mar 2015, at 14:41, teor wrote:
>> Date: Sun, 22 Mar 2015 05:12:03 +0100
>> From: Sebastian Hahn
>> To: tor-dev@lists.torproject.org
>>
>> Hi there,
>>
>> we have some functions which we never call anywhere. In many cases, it
Hi there,
we have some functions which we never call anywhere. In many cases, it
appears we shouldn't delete them from the source because they "belong"
there - the thing I initially stumbled across was
ed25519_seckey_write_to_file(), for example. But I also don't see why
compiling it and potential
Hi,
I'm currently working on cleaning up the website. Our Vidalia bundles
haven't been maintained in a long time, Tor Browser is the best way to
use Tor as a client and nobody is stepping up to replace maintainership
of the windows bundles.
I'm removing the link to these bundles as well as the re
Hi there,
On 14 Dec 2014, at 20:06, Vlad Tsyrklevich wrote:
> I'm not against keeping some around, but this warning is unlikely to turn
> around the thousands that currently match this configuration--hopefully it'll
> just encourage future bridge operators to use a 'safer' configuration. The
>
Hi Jason,
On 30 Nov 2014, at 23:32, Jason Cooper wrote:
> On Sun, Nov 30, 2014 at 06:48:09PM +0100, Sebastian Hahn wrote:
>> Access via https:// has been provided for years, and should continue
>> to work without any hiccups.
>
> No issue there for folks that prefer the e
Hi there, git users!
Today, weasel changed our gitweb setup to use cgit from now on in the
wake of a migration to wheezy. This move hopefully improves speed
without taking away any needed functionality.
At the same time, we've discontinued supporting clones via the git://
Protocol. It is unauthen
Hi there,
On 21 Nov 2014, at 23:44, Damian Johnson wrote:
>> In other words, if I sorted the descriptors by "measured" value, what would
>> that order mean?
>
> I *think* that would be the ordering of 'relays who receive the most tor
> client traffic due to having a more highly weighted heuristi
On 18 Oct 2014, at 06:29, teor wrote:
> Are there no-cost, non-license-restricted compilers available for Windows
> that support C99?
>
> This could be a way out for those who don't wish to pay for the VS 2013
> upgrade.
>
> But it's a bit more of a barrier than using an existing compiler on
On 17 Oct 2014, at 18:07, M. Ziebell wrote:
> Looking at this blog post [1] even the support for C99 in VS2013 is
> limited. I don't know if tor hit the limitations, that's for you to
> decide.
>
> C99 is 15 years old ... It should be "sane" to use it.
Please also see bug #13260 and its friend
On 28 Sep 2014, at 16:33, Tom Ritter wrote:
> On 28 September 2014 07:00, Sebastian Hahn wrote:
>> This analysis doesn't make much sense, I'm afraid. We use compression
>> on the wire, so repeating flags as human-readable strings has a much
>> lower overhead tha
On 28 Sep 2014, at 02:12, Tom Ritter wrote:
> why not also change the consensus
> and related document formats to be something more efficient than ASCII
> text? Taking the latest consensus and doing some rough estimates, I
> found the following:
>
> Original consensus, xz-ed: 407K
> Change flag
On 27 Sep 2014, at 02:18, Mike Perry wrote:
> If we were willing to tolerate 10% directory overhead this would allow
> for 5 times as many users. In other words, 100M daily connecting users.
>
> We would still need to find some way to fund the growth of the network
> to support this 40X increase
On 16 Sep 2014, at 16:15, George Kadianakis wrote:
> How guardiness works
> The idea was that the guardiness script will be an external script
> that is run by Tor in a similar fashion to the bandwidth auth
> scripts. We chose that because we could write the script in a
> high-level langu
Hi Nick,
On 25 Feb 2014, at 17:18, Nick Mathewson wrote:
> To mirror the way that authority identity keys work, we'll fully
> support keeping Ed25519 identity keys offline; they'll be used to
> sign long-ish term signing keys, which in turn will do all of the
> heavy lifting. A signing k
On 18 Apr 2014, at 21:56, Nick Mathewson wrote:
> Thanks! I've added this as proposal 235.
Code review down to 0.2.3.x has shown that the naming-related code
hasn't changed much at all, and no issues were found which would mean a
Named-flag free consensus would cause any problems.
gabelmoo and
On 02 Aug 2014, at 21:25, Daniel Martí wrote:
> This is the fifth status report of my Google Summer of Code project,
> which is to implement consensus diffs for Tor. My mentors - Sebastian and
> Nick - and myself usually hold meetings on IRC on wednesday at 16h UTC.
14h UTC.
__
On 18 Apr 2014, at 19:52, Nick Mathewson wrote:
> Imo we _should_ check through the code for things related to the Named
> flag, though, back through 0.2.3 or maybe 0.2.2. Reasons:
>
> * Private networks never worked very well with older tors.
> * Maybe there's some piece of obscure functiona
On 18 Apr 2014, at 15:02, Karsten Loesing wrote:
> If I understand the proposal correctly, operators will still be able to
> name their relay or bridge, and people can still find it in Atlas or
> Globe by this nickname. If so, great!
Yes, this is in no way related to the nickname field.
>> T
Filename: xxx-kill-named-flag.txt
Title: Stop assigning (and eventually supporting) the Named flag
Authors: Sebastian Hahnn
Created: 10 April 2014
Target: 0.2.5
Status: Draft
1. Intro and motivation
Currently, Tor supports the c
On Apr 30, 2013, at 3:17 AM, Sreenatha Bhatlapenumarthi
wrote:
> Hi,
>
> My name is Sreenatha Bhatlapenumarthi. I'd like to migrate TorBEL
> from TorCtl to Stem as a part of GSoC'13 project this summer.
Hi Sreenatha,
great to hear from you!
> Damian pointed out that there is still some impro
On Sep 1, 2012, at 1:02 AM, Roger Dingledine wrote:
> On Sat, Sep 01, 2012 at 12:36:51AM +0200, Linus Nordberg wrote:
>> Just a thought. A few of the directory authorities, I think at least
>> three, as well as the bridge authority run packages/ports only, not
>> builds from source. We'd have to
On May 5, 2012, at 3:30 PM, Gisle Vanem wrote:
> There are 2 problems with the use of 'stricmp()' (line 295) in tinytest.c.
>
> 1. As it is now, I'm getting an undefined reference to 'stricmp' when
> linking tinytest.exe and using '-nodefault:oldnames' in the link-flags. Can
> we please remo
On Mar 17, 2012, at 8:37 AM, Christian Kujau wrote:
> Hi,
>
> these ever so long law.cornell.edu URLs are now automatically redirecting
> to a shorter version - let's use that in our tor-exit-notice.html as well.
>
> Christian.
Hi, and thanks for the patch. I've filed a trac ticket[0] for thi
On Feb 10, 2012, at 12:02 AM, Robert Ransom wrote:
> The sole exception to ‘non-safe cookie authentication must die’ is
> when a controller knows that it is connected to a server process with
> equal or greater access to the same filesystem it has access to. In
> practice, this means ‘only if you
On Feb 1, 2012, at 2:48 AM, Watson Ladd wrote:
> On Tue, Jan 31, 2012 at 2:57 PM, Nick Mathewson wrote:
>> Another possibility is this:
>>
>> Browser's resolver -> Tor Client (as DNSPort): "Resolve
>> www.example.com, give me an A, and give me DNSSec stuff too."
>> Tor Client-> Tor net-> Tor Exi
On Jan 23, 2012, at 2:38 AM, Nathan Freitas wrote:
> It is legal on Android, but I have always been concerned about that sort
> of secondary download from a Tor perspective, in that you would want to
> make sure it was downloaded through the Tor network itself, right?
>
> Maybe I can just create
On Jan 20, 2012, at 1:48 AM, Nathan Freitas wrote:
> Is it the geoip database only required if you are specifying
> Exit/Entrances nodes by country code?
>
> I am thinking about not fully unpacking it into Android storage, unless
> the user activates those option in Orbot. This will save quite a
Filename: xxx-store-bridge-information.txt
Title: Automatically retrieve and store information about bridges
Author: Sebastian Hahn
Created: 16-Nov-2011
Status: Open
Target: 0.2.[45].x
Overview:
Currently, tor already stores some information about the bridges it is
configured to use locally, but
On Nov 25, 2011, at 9:58 PM, Sebastian Hahn wrote:
> On Nov 25, 2011, at 9:27 PM, Sebastian Hahn wrote:
>> I have since become convinced that it would be better to get
>> this implemented quickly, even if it doesn't have a generic
>> "prevent this param from bei
On Nov 25, 2011, at 9:27 PM, Sebastian Hahn wrote:
> I have since become convinced that it would be better to get
> this implemented quickly, even if it doesn't have a generic
> "prevent this param from being set" mechanism. I would thus like
> to change the prop
On May 4, 2011, at 7:20 AM, Sebastian Hahn wrote:
> On May 4, 2011, at 2:49 AM, Nick Mathewson wrote:
>> On Mon, May 2, 2011 at 5:23 AM, Sebastian Hahn wrote:
>>> On Mar 2, 2011, at 8:06 AM, Nick Mathewson wrote:
>>>> On Tue, Feb 22, 2011 at 1:34 AM, Sebas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey there people who have repositories hosted on tpo hardware,
weasel migrated cupani to our shiny new VM server. Along with this came
a change of ssh host key, so please be ready to modify your known_hosts
file accordingly when you next push. The new
On Sep 2, 2011, at 2:46 PM, Karsten Loesing wrote:
> Hi Andrew,
>
> On 9/2/11 2:18 AM, Andrew Lewman wrote:
>> On Thursday, August 25, 2011 04:08:00 Karsten Loesing wrote:
>>> we have been discussing sanitizing and publishing our web server logs
>>> for quite a while now. The idea is to remove
On May 4, 2011, at 2:49 AM, Nick Mathewson wrote:
> On Mon, May 2, 2011 at 5:23 AM, Sebastian Hahn wrote:
>>
>> On Mar 2, 2011, at 8:06 AM, Nick Mathewson wrote:
>>
>>> On Tue, Feb 22, 2011 at 1:34 AM, Sebastian Hahn wrote:
>>>
>>>> Desi
On May 2, 2011, at 11:23 AM, Sebastian Hahn wrote:
> On Mar 2, 2011, at 8:06 AM, Nick Mathewson wrote:
>> This is possibly bikeshed, but I would suggest that instead of
>> requiring half of existing authorities to vote on a particular
>> parameter, we require 3 or more
On Mar 2, 2011, at 8:06 AM, Nick Mathewson wrote:
> On Tue, Feb 22, 2011 at 1:34 AM, Sebastian Hahn wrote:
>
>> Design:
>>
>> When the consensus is generated, the directory authorities ensure that
>> a param is only included in the list of params if at least
Filename: xxx-param-voting.txt
Title: Require majority of authorities to vote for consensus parameters
Author: Sebastian Hahn
Created: 16-Feb-2011
Status: Draft
Overview:
The consensus that the directory authorities create may contain one or
more parameters (32-bit signed integers) that
53 matches
Mail list logo
