Re: [tor-relays] Caching new entry debian-tor...

[Tristan]

Well, until someone decides to update Orbot, Android users are still on
0.2.7.5.

On Sep 21, 2016 8:30 AM, "teor"  wrote:

>
> > On 21 Sep 2016, at 22:46, Tristan  wrote:
> >
> > Well, according to this question I asked on Tor's StackExchange, version
> 0.2.4.26 is still technically in the recommended consensus.
>
> And it will be the next to go, likely when the next directory authority's
> details change, or a serious security issue is discovered.
>
> > At any rate, running an older version is better for diversity, isn't it?
>
> Sort of, but the accumulated security fixes and performance improvements
> in later versions tend to outweigh the benefit of running a really old
> version. You'd actually contribute more to Tor's diversity by running
> 0.2.6, and even 0.2.7 isn't the most common version any more.
>
> Tim
>
> >
> >
> > On Sep 21, 2016 2:13 AM, "shraptor"  wrote:
> > On 2016-09-20 20:58, Roger Dingledine wrote:
> > On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:
> > What's up with these messages I get in tor-arm and log?
> >
> > Caching new entry debian-tor for debian-tor [62 duplicates hidden]
> >
> > What is tor doing??
> >
> > Sep 20 19:10:21.000 [notice] Caching new entry debian-tor for debian-tor
> >
> > It looks like this notice-level entry was changed to an info-level entry
> > starting in Tor 0.2.7.1-alpha:
> >
> > ...
> >
> >
> > So it looks like you are running an old version of Tor? You should
> > upgrade and the line should go away. In any case it should be harmless.
> >
> >
> > Yeah well I'm running on rpi3 and it says in tor-arm that 0.2.5 is the
> recommended
> > version for this architecture.
> >
> > Anyway I checked out your public repo's of armhf compiled tor packages.
> > These packages are unfortunately dependent on libsystemd that is not
> welcome on my systems.
> > I am running devuan as OS.
> >
> > So I have looked into building a newer version myself but it is a bit
> of  jungle
> > to setup the tool chain for me.
> >
> >
> > I hadn't noticed this log-message before and had some trouble with my
> relay so felt the need to seek information.
> >
> > /scooby
> > ___
> > tor-relays mailing list
> > tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> > ___
> > tor-relays mailing list
> > tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
> 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
>
>
>
>
>
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Caching new entry debian-tor...

[teor]

> On 21 Sep 2016, at 22:46, Tristan  wrote:
> 
> Well, according to this question I asked on Tor's StackExchange, version 
> 0.2.4.26 is still technically in the recommended consensus.

And it will be the next to go, likely when the next directory authority's 
details change, or a serious security issue is discovered.

> At any rate, running an older version is better for diversity, isn't it?

Sort of, but the accumulated security fixes and performance improvements in 
later versions tend to outweigh the benefit of running a really old version. 
You'd actually contribute more to Tor's diversity by running 0.2.6, and even 
0.2.7 isn't the most common version any more.

Tim

> 
> 
> On Sep 21, 2016 2:13 AM, "shraptor"  wrote:
> On 2016-09-20 20:58, Roger Dingledine wrote:
> On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:
> What's up with these messages I get in tor-arm and log?
> 
> Caching new entry debian-tor for debian-tor [62 duplicates hidden]
> 
> What is tor doing??
> 
> Sep 20 19:10:21.000 [notice] Caching new entry debian-tor for debian-tor
> 
> It looks like this notice-level entry was changed to an info-level entry
> starting in Tor 0.2.7.1-alpha:
> 
> ...
> 
> 
> So it looks like you are running an old version of Tor? You should
> upgrade and the line should go away. In any case it should be harmless.
> 
> 
> Yeah well I'm running on rpi3 and it says in tor-arm that 0.2.5 is the 
> recommended
> version for this architecture.
> 
> Anyway I checked out your public repo's of armhf compiled tor packages.
> These packages are unfortunately dependent on libsystemd that is not welcome 
> on my systems.
> I am running devuan as OS.
> 
> So I have looked into building a newer version myself but it is a bit of  
> jungle
> to setup the tool chain for me.
> 
> 
> I hadn't noticed this log-message before and had some trouble with my relay 
> so felt the need to seek information.
> 
> /scooby
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

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








signature.asc
Description: Message signed with OpenPGP using GPGMail
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Caching new entry debian-tor...

[Tristan]

Whoops, forgot to paste the link:
https://tor.stackexchange.com/questions/12638/how-old-is-too-old-tor-versions

On Sep 21, 2016 7:46 AM, "Tristan"  wrote:

> Well, according to this question I asked on Tor's StackExchange, version
> 0.2.4.26 is still technically in the recommended consensus.
>
> At any rate, running an older version is better for diversity, isn't it?
>
> On Sep 21, 2016 2:13 AM, "shraptor"  wrote:
>
>> On 2016-09-20 20:58, Roger Dingledine wrote:
>>
>>> On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:
>>>
 What's up with these messages I get in tor-arm and log?

 Caching new entry debian-tor for debian-tor [62 duplicates hidden]

 What is tor doing??

 Sep 20 19:10:21.000 [notice] Caching new entry debian-tor for debian-tor

>>>
>>> It looks like this notice-level entry was changed to an info-level entry
>>> starting in Tor 0.2.7.1-alpha:
>>>
>>
>> ...
>>
>>
>>> So it looks like you are running an old version of Tor? You should
>>> upgrade and the line should go away. In any case it should be harmless.
>>>
>>
>>
>> Yeah well I'm running on rpi3 and it says in tor-arm that 0.2.5 is the
>> recommended
>> version for this architecture.
>>
>> Anyway I checked out your public repo's of armhf compiled tor packages.
>> These packages are unfortunately dependent on libsystemd that is not
>> welcome on my systems.
>> I am running devuan as OS.
>>
>> So I have looked into building a newer version myself but it is a bit of
>> jungle
>> to setup the tool chain for me.
>>
>>
>> I hadn't noticed this log-message before and had some trouble with my
>> relay so felt the need to seek information.
>>
>> /scooby
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Caching new entry debian-tor...

[Tristan]

Well, according to this question I asked on Tor's StackExchange, version
0.2.4.26 is still technically in the recommended consensus.

At any rate, running an older version is better for diversity, isn't it?

On Sep 21, 2016 2:13 AM, "shraptor"  wrote:

> On 2016-09-20 20:58, Roger Dingledine wrote:
>
>> On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:
>>
>>> What's up with these messages I get in tor-arm and log?
>>>
>>> Caching new entry debian-tor for debian-tor [62 duplicates hidden]
>>>
>>> What is tor doing??
>>>
>>> Sep 20 19:10:21.000 [notice] Caching new entry debian-tor for debian-tor
>>>
>>
>> It looks like this notice-level entry was changed to an info-level entry
>> starting in Tor 0.2.7.1-alpha:
>>
>
> ...
>
>
>> So it looks like you are running an old version of Tor? You should
>> upgrade and the line should go away. In any case it should be harmless.
>>
>
>
> Yeah well I'm running on rpi3 and it says in tor-arm that 0.2.5 is the
> recommended
> version for this architecture.
>
> Anyway I checked out your public repo's of armhf compiled tor packages.
> These packages are unfortunately dependent on libsystemd that is not
> welcome on my systems.
> I am running devuan as OS.
>
> So I have looked into building a newer version myself but it is a bit of
> jungle
> to setup the tool chain for me.
>
>
> I hadn't noticed this log-message before and had some trouble with my
> relay so felt the need to seek information.
>
> /scooby
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Caching new entry debian-tor...

[shraptor]

On 2016-09-20 20:58, Roger Dingledine wrote:

On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:

What's up with these messages I get in tor-arm and log?

Caching new entry debian-tor for debian-tor [62 duplicates hidden]

What is tor doing??

Sep 20 19:10:21.000 [notice] Caching new entry debian-tor for 
debian-tor


It looks like this notice-level entry was changed to an info-level 
entry

starting in Tor 0.2.7.1-alpha:


...



So it looks like you are running an old version of Tor? You should
upgrade and the line should go away. In any case it should be harmless.



Yeah well I'm running on rpi3 and it says in tor-arm that 0.2.5 is the 
recommended

version for this architecture.

Anyway I checked out your public repo's of armhf compiled tor packages.
These packages are unfortunately dependent on libsystemd that is not 
welcome on my systems.

I am running devuan as OS.

So I have looked into building a newer version myself but it is a bit of 
 jungle

to setup the tool chain for me.


I hadn't noticed this log-message before and had some trouble with my 
relay so felt the need to seek information.


/scooby
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Caching new entry debian-tor...

[Roger Dingledine]

On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:
> What's up with these messages I get in tor-arm and log?
> 
> Caching new entry debian-tor for debian-tor [62 duplicates hidden]
> 
> What is tor doing??
> 
> Sep 20 19:10:21.000 [notice] Caching new entry debian-tor for debian-tor

It looks like this notice-level entry was changed to an info-level entry
starting in Tor 0.2.7.1-alpha:

$ git show 251f6cfc
commit 251f6cfcd829d3f7b8ac7bce8477a6e14ad47a1e
Author: Nick Mathewson 
Date:   Thu Feb 19 12:30:34 2015 -0500

Quiet "caching debian-tor for debian-tor" notice

diff --git a/src/common/compat.c b/src/common/compat.c
index fde65d9..1788e32 100644
--- a/src/common/compat.c
+++ b/src/common/compat.c
@@ -1793,8 +1793,8 @@ tor_getpwnam(const char *username)
   if ((pw = getpwnam(username))) {
 tor_passwd_free(passwd_cached);
 passwd_cached = tor_passwd_dup(pw);
-log_notice(LD_GENERAL, "Caching new entry %s for %s",
-   passwd_cached->pw_name, username);
+log_info(LD_GENERAL, "Caching new entry %s for %s",
+ passwd_cached->pw_name, username);
 return pw;
   }

So it looks like you are running an old version of Tor? You should
upgrade and the line should go away. In any case it should be harmless.

Hope that helps,
--Roger

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays