> It - plus the follow up from that many contributors - did answer my questions
> apart from two left:
>
> - should only Markus be contacted instead of lets say at least all the folks
> with more than 2 notes to make them aware?
I contacted many of the most relevant operators with incorrect MyF
Am 27.09.2016 um 19:37 schrieb nusenu:
> pa...@web.de wrote:
>> there is that list of "potentially_dangerous_relaygroups" you published.
>> Could yo please emphasize a bit more on what brings a relay on that list,
>> apart from incorrect given MyFamily which doesnt seem to be always the case.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Personally I like what Petrusko provided the most
> In torrc, an idea...??
>
> *MyFamily http://mydomain.org/myfamily.txt*
the list being a plaintext file of fingerprints seperated by newlines,
and if the server having that family list is not in t
On 09/28/2016 02:01 PM, Chad MILLER wrote:
> So? A relay can always have behaved badly. What's the harm in you
> fraudulently claiming to be in family com.example.chadmiller ? A user's
> path won't have passed through both you and me, but you could have
> prevented traffic from passing through you
On Wed, Sep 28, 2016 at 7:08 AM, grarpamp wrote:
> On Wed, Sep 28, 2016 at 6:24 AM, Chad MILLER wrote:
> > Why isn't MyFamily a family name, instead of a list of members? I see no
> > downside to having an unauthenticated
>
> Because anyone can assert the string and
> shared strings can't cross
On Wed, Sep 28, 2016 at 6:24 AM, Chad MILLER wrote:
> Why isn't MyFamily a family name, instead of a list of members? I see no
> downside to having an unauthenticated
Because anyone can assert the string and
shared strings can't cross certify each other.
__
Why isn't MyFamily a family name, instead of a list of members? I see no
downside to having an unauthenticated advisory
don't-route-through-me-if-you-also-route-through...
So, all of my nodes could have
MyFamilyName org.example
On Sep 28, 2016 05:52, "Roman Mamedov" wrote:
> On Wed, 28 Sep 201
On 28.09.2016 11:52, Roman Mamedov wrote:
> We're talking MyFamily, so it's you who is in control of all the
> nicknames, and it's only by your whim they may or may not change.
And your point is what? When I last opted for a different naming scheme,
I only had to verify that the names were not al
On Wed, 28 Sep 2016 11:41:16 +0200
Ralph Seichter wrote:
> Key fingerprints are technically much closer to being IDs than nicknames,
> which are nothing but short strings that can - and do - change at a whim.
We're talking MyFamily, so it's you who is in control of all the nicknames,
and it's on
On 28.09.2016 08:53, Roman Mamedov wrote:
> Any actual rationale, other than "do as I say"? And aside from linking
> to the man page which doesn't provide one EITHER.
Key fingerprints are technically much closer to being IDs than nicknames,
which are nothing but short strings that can - and do -
On Wed, Sep 28, 2016 at 2:53 AM, Roman Mamedov wrote:
> Any actual rationale, other than "do as I say"? And aside from linking to the
> man page which doesn't provide one EITHER.
The ambiguity problems are long known, leading to it going away.
Feel free to search historical references and better
On Wed, 28 Sep 2016 11:53:51 +0500
Roman Mamedov wrote:
> The only problem I can imagine with this is that Nefarious People can run a
same nickname relay *
--
With respect,
Roman
pgp6uN5Itqc5L.pgp
Description: OpenPGP digital signature
___
tor-rel
On Wed, 28 Sep 2016 02:38:37 -0400
grarpamp wrote:
> On Tue, Sep 27, 2016 at 4:38 PM, Roman Mamedov wrote:
> > *) Give up on listing fingerprints, instead simply list nicknames.
>
> No. Fingerprints are what to use here. Please do not use nicknames.
Any actual rationale, other than "do as I sa
In torrc, an idea...??
*MyFamily http://mydomain.org/myfamily.txt*
So > there will be only 1 list to update / maintain by the operator(s).
Ctrl+F to find if a fingerprint is already here (for lazy guyz)... if
not, Ctrl-V to add the new fingerprint,
if Atlas shows a down fingerprint, Ctrl+F too...
On Tue, Sep 27, 2016 at 4:38 PM, Roman Mamedov wrote:
> *) Give up on listing fingerprints, instead simply list nicknames.
No. Fingerprints are what to use here. Please do not use nicknames.
Ignoring the ambiguous assertions you'd be making with nicks,
it inserts the same ambiguity into downstrea
>> -Original Message-
>> From: noc@babylon.network
>
>> Always watching my ass to be a good old .
>
> Watching your arse or watching an ass are both odd things to do
Presuming that is North Amerca as winter is approaching it would be good to
cover your ass.
__
> -Original Message-
> From: noc@babylon.network
> Always watching my ass to be a good old .
Watching your arse or watching an ass are both odd things to do
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torpro
> To possibly simplify this a bit, consider that:
> *) It doesn't hurt anything if a node has itself listed in its own
> MyFamily.
> You can just use the same MyFamily string in all your configs.
> Roman
Would that unknown fact be the reason so many MyFamily sections are botched?
With changing f
>> Always watching my ass to be a good old Tor operator, I got my
>> nodes on the list. Always fun to see how one time not updating all
>> your MyFamily's gets you marked for life xD
>>
>> Time for some conf-updating.
>
> To possibly simplify this a bit, consider that:
>
> *) It doesn't hurt any
On Tue, 27 Sep 2016 21:24:59 +0200
Tim Semeijn wrote:
> Always watching my ass to be a good old Tor operator, I got my nodes on
> the list. Always fun to see how one time not updating all your
> MyFamily's gets you marked for life xD
>
> Time for some conf-updating.
To possibly simplify this a
Sounds like CloudFlare's threat policy.
On Sep 27, 2016 2:36 PM, "Tim Semeijn" wrote:
> Always watching my ass to be a good old Tor operator, I got my nodes on
> the list. Always fun to see how one time not updating all your
> MyFamily's gets you marked for life xD
>
> Time for some conf-updatin
> Always watching my ass to be a good old Tor operator, I got my nodes on
> the list. Always fun to see how one time not updating all your
> MyFamily's gets you marked for life xD
>
> Time for some conf-updating.
I wouldn't bother doing that manually.
I guess a good lazy operator automates all t
Always watching my ass to be a good old Tor operator, I got my nodes on
the list. Always fun to see how one time not updating all your
MyFamily's gets you marked for life xD
Time for some conf-updating.
On 27/09/16 19:37, nusenu wrote:
> pa...@web.de wrote:
>> there is that list of "potentially_d
pa...@web.de wrote:
> there is that list of "potentially_dangerous_relaygroups" you published.
> Could yo please emphasize a bit more on what brings a relay on that list,
> apart from incorrect given MyFamily which doesnt seem to be always the case.
> I mean I see quite a few well respected names
24 matches
Mail list logo
