{"action":"opened","issue":{"url":"https://api.github.com/repos/bailey27/cppcryptfs/issues/23","repository_url":"https://api.github.com/repos/bailey27/cppcryptfs","labels_url":"https://api.github.com/repos/bailey27/cppcryptfs/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/bailey27/cppcryptfs/issues/23/comments","events_url":"https://api.github.com/repos/bailey27/cppcryptfs/issues/23/events","html_url":"https://github.com/bailey27/cppcryptfs/issues/23","id":307228046,"number":23,"title":"Reverse mode fileystems are always mounted read-only","user":{"login":"Wihlelm","id":5161485,"avatar_url":"https://avatars1.githubusercontent.com/u/5161485?v=4","gravatar_id":"","url":"https://api.github.com/users/Wihlelm","html_url":"https://github.com/Wihlelm","followers_url":"https://api.github.com/users/Wihlelm/followers","following_url":"https://api.github.com/users/Wihlelm/following{/other_user}","gists_url":"https://api.github.com/users/Wihlelm/gists{/gist_id}","starred_url":"https://api.github.com/users/Wihlelm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Wihlelm/subscriptions","organizations_url":"https://api.github.com/users/Wihlelm/orgs","repos_url":"https://api.github.com/users/Wihlelm/repos","events_url":"https://api.github.com/users/Wihlelm/events{/privacy}","received_events_url":"https://api.github.com/users/Wihlelm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-21T12:39:36Z","updated_at":"2018-03-21T12:39:36Z","closed_at":null,"author_association":"NONE","body":"Hi bailey27,\r\n\r\nfirst of all, thank you for your port of gocryptfs in windows.\r\n\r\nCan you explain why reverse mode fileystems are always mounted read-only ? For backup it is perfectly fine, but what about synchronization with a sync client ? For example two different computers where files are stored unencrypted which sync through a cloud where files are stored encrypted ? Any modification on one side should propagate to the other. Moreover, most of sync clients needs to have write access to store a local journal of the sync process inside the sync directory.\r\n\r\nIs it inherent to the program ? Is it not possible to allow to bypass this default option of read-only to give write access ?\r\n\r\nBest regards\r\n"}}
{"actor":{"display_login":"Wihlelm"}}