summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorAdam Ierymenko <adam.ierymenko@gmail.com>2015-07-23 17:18:20 -0700
committerAdam Ierymenko <adam.ierymenko@gmail.com>2015-07-23 17:18:20 -0700
commitd647a587a1c920cdf58ce77872280e4e4ec9cca9 (patch)
tree0a548e6819a26eab49fc8a3670aff915fd0560c0 /include
parenta493fc23f4305f80d93f0879324aa87f536a1a90 (diff)
downloadinfinitytier-d647a587a1c920cdf58ce77872280e4e4ec9cca9.tar.gz
infinitytier-d647a587a1c920cdf58ce77872280e4e4ec9cca9.zip
(1) Fix updating of network revision counter on member change.
(2) Go back to timestamp as certificate revision number. This is simpler and more robust than using the network revision number for this and forcing network revision fast-forward, which could cause some peers to fall off the horizon when you don't want them to.
Diffstat (limited to 'include')
-rw-r--r--include/ZeroTierOne.h11
1 files changed, 0 insertions, 11 deletions
diff --git a/include/ZeroTierOne.h b/include/ZeroTierOne.h
index 7ae524a8..dc2243f2 100644
--- a/include/ZeroTierOne.h
+++ b/include/ZeroTierOne.h
@@ -106,17 +106,6 @@ extern "C" {
#define ZT1_MAX_PEER_NETWORK_PATHS 4
/**
- * Maximum number of revisions over which a network COM can differ and still be in-horizon (agree)
- *
- * This is the default max delta for the revision field in COMs issued
- * by network controllers, and is defined here for documentation purposes.
- * When a network is changed so as to de-authorize a member, its revision
- * should be incremented by this number. Otherwise all other changes that
- * materially affect the network should result in increment by one.
- */
-#define ZT1_CERTIFICATE_OF_MEMBERSHIP_REVISION_MAX_DELTA 16
-
-/**
* Feature flag: ZeroTier One was built to be thread-safe -- concurrent processXXX() calls are okay
*/
#define ZT1_FEATURE_FLAG_THREAD_SAFE 0x00000001