[tor-dev] WIP proposal for migration to TLS 1.3

2018-01-22 Thread isis agora lovecruft 
Hello,

It's not done yet; it probably has errors; it definitely has omissions; it's
still riddled with "XXX"s everywhere… but here's a work-in-progress draft
proposal for migrating our link protocol(s) to use TLS 1.3:

https://gitweb.torproject.org/user/isis/torspec.git/log/?h=tls13

It's not quite ready for a whole bunch of feedback yet, since I'm still
reading through all the specs and writing the proposal. However, if you're
super knowledgeable about TLS 1.3 and have opinions or ideas or see a
mistake/misunderstanding somewhere, please feel free to share!  Thanks!

Best regards,
-- 
 ♥Ⓐ isis agora lovecruft
_
OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
Current Keys: https://fyb.patternsinthevoid.net/isis.txt


signature.asc
Description: Digital signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] onionoo.tpo stuck at 2018-01-21 22:00

2018-01-22 Thread nusenu 
> Looks like the primary CollecTor instance had a problem between 22:00
> and 08:00 UTC. It works again now, as does Onionoo.

Karsten, thanks for the fast reaction.

> We didn't lose any data, because the primary CollecTor instance obtained
> all descriptors it had missed earlier from the backup CollecTor instance.


Since I'm archiving onionoo data I'm "loosing" data (causing blind spots) 
everytime a "relays_published" 
timestamp is skipped. In theory one could spin up an onionoo instance to 
generate data for skipped
timestamps but in practice this is hard (requires lots of resources). 
(I know, you are probably talking about not loosing any raw CollecTor data, but 
wanted to mention that
nonetheless.)

Do you monitor onionoo for such problems ("relays_published" timestamp 
remaining unchanged for >1-2 hours)? 
Would you find something like that useful?

Thanks for keeping it running besides all the other things you do. 

I'm wondering if the admin team would be available to cover such cases to reduce
the operations load for developers.

kind regards,
nusenu


-- 
https://mastodon.social/@nusenu
twitter: @nusenu_



signature.asc
Description: OpenPGP digital signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] onionoo.tpo stuck at 2018-01-21 22:00

2018-01-22 Thread Karsten Loesing 
On 2018-01-22 09:03, nusenu wrote:
> Hi Karsten,

Hi nusenu,

> just wanted to let you know that the delta between
> relays_published and current time is unusually high.
> 
> 
> https://onionoo.torproject.org/details?limit=0
> 
> {"version":"5.0",
> "build_revision":"0bce98a",
> "relays_published":"2018-01-21 22:00:00",
> 
> This is currently blocking ornetradar reports.

Looks like the primary CollecTor instance had a problem between 22:00
and 08:00 UTC. It works again now, as does Onionoo.

We didn't lose any data, because the primary CollecTor instance obtained
all descriptors it had missed earlier from the backup CollecTor instance.

> thanks for having a look,

Thanks for the report!

> nusenu

All the best,
Karsten



signature.asc
Description: OpenPGP digital signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

[tor-dev] onionoo.tpo stuck at 2018-01-21 22:00

2018-01-22 Thread nusenu 
Hi Karsten,

just wanted to let you know that the delta between
relays_published and current time is unusually high.


https://onionoo.torproject.org/details?limit=0

{"version":"5.0",
"build_revision":"0bce98a",
"relays_published":"2018-01-21 22:00:00",

This is currently blocking ornetradar reports.

thanks for having a look,
nusenu


-- 
https://mastodon.social/@nusenu
twitter: @nusenu_



signature.asc
Description: OpenPGP digital signature
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev