From 5481d60a470cd70be5a96b4e674987f41b4481b7 Mon Sep 17 00:00:00 2001 From: "Kali Kaneko (leap communications)" Date: Thu, 15 Dec 2016 09:03:39 +0100 Subject: [docs] fix typos --- src/leap/bitmask/core/_session.py | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) (limited to 'src') diff --git a/src/leap/bitmask/core/_session.py b/src/leap/bitmask/core/_session.py index 24070a8..9b22f15 100644 --- a/src/leap/bitmask/core/_session.py +++ b/src/leap/bitmask/core/_session.py @@ -33,15 +33,15 @@ logger = Logger() class SessionService(HookableService): """ - This service holds random local-session tokens, that will be use to protect - the access to the API resources. + This service holds random local-session tokens, that will be used to + protect the access to the API resources. These tokens are different from the (remote) SRP session tokens: the - local-session tokens are ephimeral and generated by the local Bitmask - deamon. + local-session tokens are also ephemeral, but generated by the local Bitmask + daemon. Right now, they are generated when a soledad instance is successfully - created. This might be subject to further discussion, but this is the + created. This might be subject to further discussion, but this is the earliest moment in which we can decide if a user should be authenticated locally: it means that the entered password is able to decrypt the local store. In this way, we can protect the API resources even in the case that @@ -65,6 +65,4 @@ class SessionService(HookableService): def hook_on_new_soledad_instance(self, **kw): user = kw['user'] session_token = binascii.hexlify(os.urandom(10)) - print '---------------------------------------------------' - print "hook on new soledad instance!", user, session_token self._tokens[user] = session_token -- cgit v1.2.3