{"action":"created","issue":{"url":"https://api.github.com/repos/owncloud/client/issues/4327","repository_url":"https://api.github.com/repos/owncloud/client","labels_url":"https://api.github.com/repos/owncloud/client/issues/4327/labels{/name}","comments_url":"https://api.github.com/repos/owncloud/client/issues/4327/comments","events_url":"https://api.github.com/repos/owncloud/client/issues/4327/events","html_url":"https://github.com/owncloud/client/issues/4327","id":124352406,"number":4327,"title":"Adding ownCrypt : client-side encryption","user":{"login":"orion1024","id":6241740,"avatar_url":"https://avatars3.githubusercontent.com/u/6241740?v=4","gravatar_id":"","url":"https://api.github.com/users/orion1024","html_url":"https://github.com/orion1024","followers_url":"https://api.github.com/users/orion1024/followers","following_url":"https://api.github.com/users/orion1024/following{/other_user}","gists_url":"https://api.github.com/users/orion1024/gists{/gist_id}","starred_url":"https://api.github.com/users/orion1024/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orion1024/subscriptions","organizations_url":"https://api.github.com/users/orion1024/orgs","repos_url":"https://api.github.com/users/orion1024/repos","events_url":"https://api.github.com/users/orion1024/events{/privacy}","received_events_url":"https://api.github.com/users/orion1024/received_events","type":"User","site_admin":false},"labels":[{"id":120033841,"url":"https://api.github.com/repos/owncloud/client/labels/enhancement%20-%20proposed","name":"enhancement - proposed","color":"FF9900","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":88,"created_at":"2015-12-30T14:09:35Z","updated_at":"2017-08-20T16:43:50Z","closed_at":null,"body":"Hello,\n\nThis issue is created so that we can discuss the details on how ownCrypt should be integrated in the current code, both for the initial integration and as work on it progresses.\n## Some discussion material\n### General documentation about ownCrypt\n- [Design, intents and features](https://cloud.airmail.fr/public.php?service=files&t=a9fe1a55a59374dd6bc399f4ff4d60db) (finished)\n- Crypto design :\n  - [Crypto design](https://cloud.airmail.fr/public.php?service=files&t=d475f3c9d77e99d8b413977729be5f0e) (ongoing work)\n  - [Crypto design basic graph](https://cloud.airmail.fr/index.php/s/2AgPkL5cxeXFVul) (finished)\n  - [Crypto design advanced graph](https://cloud.airmail.fr/index.php/s/QWWtS64NwqjSjBW) (finished)\n### Integration discussion\n\nTo start the discussion [I created a more specific document](https://cloud.airmail.fr/index.php/s/uqXpyMmv8AESSA8).\n\nHere is a quick brief of its content :\n- **Section 1 to 3** is an analysis of the sync algorithm code.\n- **Section 4 is where I detailed my proposal and what needs to be discussed with the client team.**\n\nWhile **section 1** is for the most part a verbose description of what the code does, and not very interesting for someone familiar with the existing code, **section 2 and 3** are more \"meta\" and are an attempt at documenting things to get a better overall understanding of the code structure.\nNB : Section 1 to 3 are not completely finished but most of the remaining analysis is not critical for the initial integration.\n\nI also created a \"state graph\" that describes how the discovery and reconcile phase decides what to do with each file. [This is the graph](https://cloud.airmail.fr/index.php/s/XgbRGN8Mwa9Vlnz) (not included here because it too big).\n\nWhile not very useful for someone who knows this by heart, it is a good reference when one needs (for instance) to know the possible paths for how an item could end up with the XXXX instruction.\n## Next steps\n\n@ogoffart @danimo @dragotin @jturcotte \n### Starting point\n\n**The first thing I would like to do is reach an agreement with the client team on the proposals I made in the document**, so that I can start coding.\nFurther discussion will be needed on other topics after this one, but I believe this is the most structuring code-wise.\n### Integration tests\n\nI plan to use Jenkins to run proper integration tests. Is there any templates I could use to speed up the initial set up of Jenkins (for instance, to configure the building test) ?\n\nI'm also considering tools [such as Sikuli](http://www.sikuli.org) to test more things than the current torture tests. I read about Smashbox but it seems more about testing server-side functionality.\nComprehensive integration tests are pretty critical for ownCrypt since it will be implemented in the deepest layer of the client, so the risk of introducing regression is great.\n\r\n\r\n<bountysource-plugin>\r\n---\r\nWant to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29483452-adding-owncrypt-client-side-encryption?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github).\r\n</bountysource-plugin>"},"comment":{"url":"https://api.github.com/repos/owncloud/client/issues/comments/323596787","html_url":"https://github.com/owncloud/client/issues/4327#issuecomment-323596787","issue_url":"https://api.github.com/repos/owncloud/client/issues/4327","id":323596787,"user":{"login":"orion1024","id":6241740,"avatar_url":"https://avatars3.githubusercontent.com/u/6241740?v=4","gravatar_id":"","url":"https://api.github.com/users/orion1024","html_url":"https://github.com/orion1024","followers_url":"https://api.github.com/users/orion1024/followers","following_url":"https://api.github.com/users/orion1024/following{/other_user}","gists_url":"https://api.github.com/users/orion1024/gists{/gist_id}","starred_url":"https://api.github.com/users/orion1024/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orion1024/subscriptions","organizations_url":"https://api.github.com/users/orion1024/orgs","repos_url":"https://api.github.com/users/orion1024/repos","events_url":"https://api.github.com/users/orion1024/events{/privacy}","received_events_url":"https://api.github.com/users/orion1024/received_events","type":"User","site_admin":false},"created_at":"2017-08-20T16:43:50Z","updated_at":"2017-08-20T16:43:50Z","body":"Also note that few work has been done on ownCrypt, so if something comes out of cryptomator-related efforts it would be good news.\nThe main issue I have with current cryptomator implementation is that it doesn't allow for file sharing, which is a big barrier to adoption.\n\n> Le 19 août 2017 à 12:44, e-alfred <notifications@github.com> a écrit :\n> \n> Cryptomator for mobile is \"Open Core\". The libraries used are Open Source, the desktop clients are fully Open Source.\n> \n> The Nextcloud announcement says they are examining how they could integrate it. It would be nice if something comes from that, for sure.\n> \n> —\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub, or mute the thread.\n> \n"}}
{"actor":{"display_login":"orion1024"}}