mesalab_git/zhangyang/zerotierone.git - Repository for zhangyang/zerotierone

Age	Commit message (Collapse)	Author
2021-05-24	Basic plumbing for authentication requirement and piping through of URL ↵	Adam Ierymenko
	information.
2020-08-20	BSL date bump	Adam Ierymenko

2019-08-23	Relicense: GPLv3 -> ZeroTier BSL 1.1	Adam Ierymenko

2019-01-14	Updated licenses for 2019	Joseph Henry

2018-01-08	Copyright updates for 2018.	Adam Ierymenko

2017-04-27	License header update.	Adam Ierymenko

2017-03-06	Send revocations automatically on deauth for instant kill, also fix some ↵	Adam Ierymenko
	issues with the RP.
2016-11-10	Refactor controller to permit sending of pushes as well as just replies to ↵	Adam Ierymenko
	config requests.
2016-08-09	Encode and decode of tags and capabilities in NetworkConfig.	Adam Ierymenko

2016-06-21	Make Dictionary templatable so it can be used where we want a higher capacity.	Adam Ierymenko

2016-06-16	Big refactor mostly builds. We now have a uniform backward compatible netconf.	Adam Ierymenko

2016-05-06	Simplify a bunch of NetworkConfig stuff by eliminating accessors, also makes ↵	Adam Ierymenko
	network controller easier to refactor.
2016-01-12	boring doc stuff	Adam Ierymenko

2015-09-08	Add a bit of useful testing instrumentation to SqliteNetworkController.	Adam Ierymenko

2015-07-23	Add a rate limiting circuit breaker to the network controller to prevent ↵	Adam Ierymenko
	flooding attacks and race conditions.
2015-07-23	Eliminate some poorly thought out optimizations from the netconf/controller ↵	Adam Ierymenko
	interaction, and go ahead and bump version to 1.0.4. For a while in 1.0.3 -dev I was trying to optimize out repeated network controller requests by using a ratcheting mechanism. If the client received a network config that was indeed different from the one it had, it would respond by instantlly requesting it again. Not sure what I was thinking. It's fundamentally unsafe to respond to a message with another message of the same type -- it risks a race condition. In this case that's exactly what could happen. It just isn't worth the added complexity to avoid a tiny, tiny amount of network overhead, so I've taken this whole path out. A few extra bytes every two minutes isn't worth fretting about, but as I recall the reason for this optimization was to save CPU on the controller. This can be achieved by just caching responses in memory there and serving those same responses back out if they haven't changed. I think I developed that 'ratcheting' stuff before I went full time on this. It's hard to develop stuff like this without hours of sustained focus.
2015-04-15	More cleanup, and fix for the extremely unlikely case of identity collision.	Adam Ierymenko

2015-04-15	Putting the main binary back together...	Adam Ierymenko

2015-04-15	Rename netconf to controller and NetworkConfigMaster to NetworkController ↵	Adam Ierymenko
	for consistency.