summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRuben Pollan <meskio@sindominio.net>2014-10-30 21:57:48 -0600
committerRuben Pollan <meskio@sindominio.net>2014-11-04 11:53:27 -0600
commitfe41ebea35e17abb402b2ba0d786897ac102e760 (patch)
tree39e13aa71e71b320dd0ffdaf0aab306e58ca5ff3
parent1fac28ed61bde2b8db8cff8aea45b20705a072e3 (diff)
Remove outdated comment
-rw-r--r--keymanager/src/leap/keymanager/keys.py11
1 files changed, 1 insertions, 10 deletions
diff --git a/keymanager/src/leap/keymanager/keys.py b/keymanager/src/leap/keymanager/keys.py
index ecb0a36a..b5c9118d 100644
--- a/keymanager/src/leap/keymanager/keys.py
+++ b/keymanager/src/leap/keymanager/keys.py
@@ -141,16 +141,7 @@ class EncryptionKey(object):
Abstract class for encryption keys.
A key is "validated" if the nicknym agent has bound the user address to a
- public key. Nicknym supports three different levels of key validation:
-
- * Level 3 - path trusted: A path of cryptographic signatures can be traced
- from a trusted key to the key under evaluation. By default, only the
- provider key from the user's provider is a "trusted key".
- * level 2 - provider signed: The key has been signed by a provider key for
- the same domain, but the provider key is not validated using a trust
- path (i.e. it is only registered)
- * level 1 - registered: The key has been encountered and saved, it has no
- signatures (that are meaningful to the nicknym agent).
+ public key.
"""
__metaclass__ = ABCMeta