Send tor-dev mailing list submissions to
tor-dev@xxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
or, via email, send a message with subject or body 'help' to
tor-dev-request@xxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
tor-dev-owner@xxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of tor-dev digest..."
Today's Topics:
1. Re: Adding depictor/stem to Jenkins (Tom Ritter)
2. Re: GeoLite ASN Database broken (Jason Ketola)
3. Re: GeoLite ASN Database (still) broken (nusenu)
4. Re: GeoLite ASN Database (still) broken (Jason Ketola)
5. Re: [network-team] [doodle poll] Meeting to discuss guard
proposal draft status (isis agora lovecruft)
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 Jul 2016 14:48:43 -0500
From: Tom Ritter <tom@xxxxxxxxx>
To: tor-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-dev] Adding depictor/stem to Jenkins
Message-ID:
<CA+cU71mHtgMRnfq3F51U+MTTDs9V9ySHgUfeyHWZ3gntuRf5eQ@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8
On 5 July 2016 at 14:34, Damian Johnson <atagar@xxxxxxxxxxxxxx> wrote:
> Hi Tom, just food for thought but another option would be a cron task
> that pulls the repos and runs that if there's a change. That's what I
> do for stem's website so it reflects the changes I push.
I think that's a good model for webpages-backed-by-git, but less so
for integration/software testing.
I could probably rig something up like that locally, but I'd have to
make it detect a crash and email me. The advantage of jenkins is it
will do that automatically, on infrastructure I don't have to worry
about maintaining[0], as well as making the crash details public.
There's a chance it might even detect a break in stem.
-tom
[0] A problem I've had a lot is that my 'email me stuff' scripts will
stop emailing... and I never find out they're failing!
------------------------------
Message: 2
Date: Tue, 5 Jul 2016 17:40:20 -0400
From: Jason Ketola <jketola@xxxxxxxxxxx>
To: tor-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-dev] GeoLite ASN Database broken
Message-ID:
<CADrFj5Aw7b0SVMmo=M33-+zdHOUKbrNr=p3zs4crUj_067agsw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hello,
I'm writing on behalf of MaxMind. We believe we have addressed the issues
you noted in the latest update of our GeoLite ASN database:
http://dev.maxmind.com/geoip/legacy/geolite/#Downloads.
Thank you for bringing the issues to our attention.
Regards,
Jason
--
Jason Ketola
Vice President, Operations
MaxMind, Inc.
www.maxmind.com
617-500-4493 x807
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20160705/78856c57/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 05 Jul 2016 22:08:00 +0000
From: nusenu <nusenu@xxxxxxxxxxxxxxx>
To: jketola@xxxxxxxxxxx
Cc: support@xxxxxxxxxxx, tor-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-dev] GeoLite ASN Database (still) broken
Message-ID: <ef8544c9-faae-aa2f-5a42-e52f0394d268@xxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hello Jason,
thanks for reporting back.
> I'm writing on behalf of MaxMind. We believe we have addressed the issues
> you noted in the latest update of our GeoLite ASN database:
> http://dev.maxmind.com/geoip/legacy/geolite/#Downloads.
>
> Thank you for bringing the issues to our attention.
I just downloaded the current version of GeoIPASNum2.zip
(SHA1: c72a275c66cededf47157e3cea4625342b85bf94)
to have a short look at it and I'm not sure the problem is fixed completely.
While the number of unnamed AS entries significantly improved (unnamed
count is down to 1462 from >57k, still not back to ~500 (Feb 2016), but
just comparing absolute numbers without considering total entries in
each CSV might be a bit flawed metric anyway),
incorrect AS names apparently remain:
I searched for the two examples I gave in my last email:
AS8708 and AS12741
they are still incorrectly named "73-75 Dr. Staicovici" and "Warszawa
02-822" in your DB, which means the problem still persists.
actual names:
http://bgp.he.net/AS8708
http://bgp.he.net/AS12741
thank you for looking into this again,
nusenu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20160705/f646772d/attachment-0001.sig>
------------------------------
Message: 4
Date: Tue, 5 Jul 2016 19:09:51 -0400
From: Jason Ketola <jketola@xxxxxxxxxxx>
To: nusenu <nusenu@xxxxxxxxxxxxxxx>
Cc: support@xxxxxxxxxxx, tor-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-dev] GeoLite ASN Database (still) broken
Message-ID:
<CADrFj5DPR3myw4AFnOuA6kqoAVuyUVeNBY=7_rNz-Xz+qetqaw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hi nusenu,
Sorry the issues aren't entirely resolved. We'll take a look at those.
Thanks,
Jason
On Tue, Jul 5, 2016 at 6:08 PM, nusenu <nusenu@xxxxxxxxxxxxxxx> wrote:
> Hello Jason,
>
> thanks for reporting back.
>
> > I'm writing on behalf of MaxMind. We believe we have addressed the issues
> > you noted in the latest update of our GeoLite ASN database:
> > http://dev.maxmind.com/geoip/legacy/geolite/#Downloads.
> >
> > Thank you for bringing the issues to our attention.
>
> I just downloaded the current version of GeoIPASNum2.zip
> (SHA1: c72a275c66cededf47157e3cea4625342b85bf94)
> to have a short look at it and I'm not sure the problem is fixed
> completely.
>
> While the number of unnamed AS entries significantly improved (unnamed
> count is down to 1462 from >57k, still not back to ~500 (Feb 2016), but
> just comparing absolute numbers without considering total entries in
> each CSV might be a bit flawed metric anyway),
> incorrect AS names apparently remain:
>
> I searched for the two examples I gave in my last email:
>
> AS8708 and AS12741
> they are still incorrectly named "73-75 Dr. Staicovici" and "Warszawa
> 02-822" in your DB, which means the problem still persists.
>
> actual names:
> http://bgp.he.net/AS8708
> http://bgp.he.net/AS12741
>
>
> thank you for looking into this again,
> nusenu
>
>
--
Jason Ketola
Vice President, Operations
MaxMind, Inc.
www.maxmind.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20160705/b50dd7b3/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 6 Jul 2016 03:44:25 +0000
From: isis agora lovecruft <isis@xxxxxxxxxxxxxx>
To: Ola Bini <obini@xxxxxxxxxxxxxxxx>, Fan Jiang
<fanjiang@xxxxxxxxxxxxxxxx>, Tania Silva <tsilva@xxxxxxxxxxxxxxxx>,
Ivan Pazmino <ipazmino@xxxxxxxxxxxxxxxx>, Reinaldo Junior
<rjunior@xxxxxxxxxxxxxxxx>, Chelsea Komlo <ckomlo@xxxxxxxxxxxxxxxx>
Cc: network-team <network-team@xxxxxxxxxxxxxxxxxxxx>,
tor-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-dev] [network-team] [doodle poll] Meeting to discuss
guard proposal draft status
Message-ID: <20160706034425.GA7419@xxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
George Kadianakis transcribed 1.6K bytes:
> Hello!
>
> With Nick we settled on Thursday at 14:00 UTC as the time for this meeting!
> The plan is to finish the meeting in strictly less than 90 minutes.
Hey George, Hey Everyone,
If we do it Thursday at 16:00 UTC (or later), I could attend, but not before,
since I will be on a flight. If it works out better for everyone else to have
it at 14:00 instead, then that's also fine with me and please just let me know
afterwards what I can do to help.
Best regards,
--
♥Ⓐ isis agora lovecruft
_________________________________________________________
OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
Current Keys: https://fyb.patternsinthevoid.net/isis.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1240 bytes
Desc: Digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20160706/26e06080/attachment-0001.sig>
------------------------------
Subject: Digest Footer
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
------------------------------
End of tor-dev Digest, Vol 66, Issue 7
**************************************
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev