diff options
Diffstat (limited to 'doc/design/assistant/cloud.mdwn')
| -rw-r--r-- | doc/design/assistant/cloud.mdwn | 29 |
1 files changed, 2 insertions, 27 deletions
diff --git a/doc/design/assistant/cloud.mdwn b/doc/design/assistant/cloud.mdwn index b815c5d2d..18a1b3e9a 100644 --- a/doc/design/assistant/cloud.mdwn +++ b/doc/design/assistant/cloud.mdwn @@ -30,7 +30,7 @@ been a change to Alice's git repo. Then he needs to pull from Alice's git repo, or some other repo in the cloud she pushed to. Once both steps are done, the assistant will transfer the file from the cloud to Bob. -* dvcs-autosync uses jabber; all repos need to have the same jabber account +* dvcs-autosync uses xmppp; all repos need to have the same xmpp account configured, and send self-messages. An alternative would be to have different accounts that join a channel or message each other. Still needs account configuration. @@ -44,32 +44,7 @@ the assistant will transfer the file from the cloud to Bob. * pubsubhubbub does not seem like an option; its hubs want to pull down a feed over http. -### jabber TODO - -* test with big servers, eg google chat -* Prevent idle disconnection. Probably means sending or receiving pings, - but would prefer to avoid eg pinging every 60 seconds as some clients do. -* Make the git-annex clients invisible, so a user can use their regular - account without always seeming to be present when git-annex is logged in. - See <http://xmpp.org/extensions/xep-0126.html> - -### jabber security - -Any data git-annex sends over this XMPP will be visible to the XMPP -account's buddies, to the XMPP server, and quite likely to other interested -parties. So it's important to consider the security exposure of using it. - -If git-annex sends only a single bit notification, this lets attackers know -when the user is active and changing files. Although the assistant's other -syncing activities can somewhat mask this. - -As soon as git-annex does anything unlike any other client, an attacker can -see how many clients are connected for a user, and fingerprint the ones -running git-annex, and determine how many clients are running git-annex. - -If git-annex sent the UUID of the remote it pushed to, this would let -attackers determine how many different remotes are being used, -and map some of the connections between clients and remotes. +See [[xmpp]] for design of git-annex's use of xmpp for notifications. ## storing git repos in the cloud |