Merge lp:~free.ekanayaka/landscape-client/exchange-token into lp:~landscape/landscape-client/trunk
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Free Ekanayaka | ||||
Approved revision: | 660 | ||||
Merged at revision: | 655 | ||||
Proposed branch: | lp:~free.ekanayaka/landscape-client/exchange-token | ||||
Merge into: | lp:~landscape/landscape-client/trunk | ||||
Diff against target: |
355 lines (+131/-14) 9 files modified
landscape/__init__.py (+4/-1) landscape/broker/exchange.py (+29/-3) landscape/broker/registration.py (+16/-2) landscape/broker/store.py (+8/-0) landscape/broker/tests/test_exchange.py (+30/-3) landscape/broker/tests/test_registration.py (+12/-0) landscape/broker/tests/test_store.py (+13/-0) landscape/broker/tests/test_transport.py (+3/-1) landscape/broker/transport.py (+16/-4) |
||||
To merge this branch: | bzr merge lp:~free.ekanayaka/landscape-client/exchange-token | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chris Glass (community) | Approve | ||
Alberto Donato (community) | Approve | ||
Review via email: mp+158131@code.launchpad.net |
Commit message
This branch implements the client-side part of the changes needed to detect cloned computers. The idea is that at each exchange the server will give the client a token that the client will be required to give back at the following exchange to prove that it's still the same client. If two clients with the same secure ID try to perform an exchange using the same token, only the first one that completes the exchange will succeed, because the second will not be authenticated since the token has changed in the meantime (after the first exchange completed).
Description of the change
This branch implements the client-side part of the changes needed to detect cloned computers. The idea is that at each exchange the server will give the client a token that the client will be required to give back at the following exchange to prove that it's still the same client. If two clients with the same secure ID try to perform an exchange using the same token, only the first one that completes the exchange will succeed, because the second will not be authenticated since the token has changed in the meantime (after the first exchange completed).
Looks good! +1
#1: _/__seattr_ _, perhaps with defaults for some parameters. Just an idea, not something for this branch anyway.
Not really related to your changes, but I see MessageStore hs a lot of getter/setters for parameters that are just passed to the persist. Maybe we could reduce duplication using __getattr_