{"action":"created","issue":{"url":"https://api.github.com/repos/nextcloud/server/issues/1413","repository_url":"https://api.github.com/repos/nextcloud/server","labels_url":"https://api.github.com/repos/nextcloud/server/issues/1413/labels{/name}","comments_url":"https://api.github.com/repos/nextcloud/server/issues/1413/comments","events_url":"https://api.github.com/repos/nextcloud/server/issues/1413/events","html_url":"https://github.com/nextcloud/server/issues/1413","id":177114766,"number":1413,"title":"Sharing between different NC-Instances not possible with selfsign Certificate","user":{"login":"zeus86","id":11415964,"avatar_url":"https://avatars.githubusercontent.com/u/11415964?v=3","gravatar_id":"","url":"https://api.github.com/users/zeus86","html_url":"https://github.com/zeus86","followers_url":"https://api.github.com/users/zeus86/followers","following_url":"https://api.github.com/users/zeus86/following{/other_user}","gists_url":"https://api.github.com/users/zeus86/gists{/gist_id}","starred_url":"https://api.github.com/users/zeus86/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zeus86/subscriptions","organizations_url":"https://api.github.com/users/zeus86/orgs","repos_url":"https://api.github.com/users/zeus86/repos","events_url":"https://api.github.com/users/zeus86/events{/privacy}","received_events_url":"https://api.github.com/users/zeus86/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nextcloud/server/labels/bug","name":"bug","color":"ee0701"},{"url":"https://api.github.com/repos/nextcloud/server/labels/feature:%20federation","name":"feature: federation","color":"c2e0c6"},{"url":"https://api.github.com/repos/nextcloud/server/labels/feature:%20sharing","name":"feature: sharing","color":"c2e0c6"},{"url":"https://api.github.com/repos/nextcloud/server/labels/needs%20info","name":"needs info","color":"006b75"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-09-15T08:08:54Z","updated_at":"2016-10-07T14:03:14Z","closed_at":null,"body":"### Steps to reproduce\r\n1. Share a file via Link in Instance A\r\n2. Open Link \r\n3. Click \"Add to your Nextcloud\"\r\n4. Enter Address of Instance B\r\n\r\n### Expected behaviour\r\nIn case of a Certificate not trusted by the OS of instance B (aka. selfsigned):\r\nPopup that says \"Cert not trusted, continue anyway?\"\r\n\r\n### Actual behaviour\r\nAction aborts due to the fact, that the Certificate is not trusted\r\n\r\n**Nextcloud version:**\r\n10.0\r\n\r\n**Updated from an older Nextcloud/ownCloud or fresh install:**\r\nfresh\r\n\r\n\r\n\r\nOf course not all users, using NC are able (or willing) to add certificates of other instances with self-sign-cert to the trusted certs of the OS of their NC-Instance. On the one hand is not every user admin on the installation he or she uses, and on the other hand might this cause problems within larger setups, which are used internal only without access to the internet.\r\n\r\nOf course i aggree that in case of public reachability something like letsencrypt shall be used (which is not always possible and might be a hassle with dyndns on home setups), and that company-networks shall use own CAs, which are installed on all productive machines, but the bitter truth is, that this is not the case, so it sould be at least possible to dismiss certificate-warnings (at least because of an untrusted signing CA) if needed, like it is in browsers. \r\n"},"comment":{"url":"https://api.github.com/repos/nextcloud/server/issues/comments/252260533","html_url":"https://github.com/nextcloud/server/issues/1413#issuecomment-252260533","issue_url":"https://api.github.com/repos/nextcloud/server/issues/1413","id":252260533,"user":{"login":"fishscene","id":1910351,"avatar_url":"https://avatars.githubusercontent.com/u/1910351?v=3","gravatar_id":"","url":"https://api.github.com/users/fishscene","html_url":"https://github.com/fishscene","followers_url":"https://api.github.com/users/fishscene/followers","following_url":"https://api.github.com/users/fishscene/following{/other_user}","gists_url":"https://api.github.com/users/fishscene/gists{/gist_id}","starred_url":"https://api.github.com/users/fishscene/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fishscene/subscriptions","organizations_url":"https://api.github.com/users/fishscene/orgs","repos_url":"https://api.github.com/users/fishscene/repos","events_url":"https://api.github.com/users/fishscene/events{/privacy}","received_events_url":"https://api.github.com/users/fishscene/received_events","type":"User","site_admin":false},"created_at":"2016-10-07T14:03:14Z","updated_at":"2016-10-07T14:03:14Z","body":"I agree completely with @zeus86. Self-signed certs should not be a problem. This is actively halting a setup I am working on.\r\nI initially reported this in the nextcloud snap: https://github.com/nextcloud/nextcloud-snap/issues/81\r\nOriginal post:\r\n-------------------------------------------------------------------\r\nFederation: Can't add trusted nextcloud server if SSL Cert is self-signed.\r\n\r\nI was attempting to run a test to link 2 snap installations of NextCloud with federation, but the following error was generated:\r\ncURL error 60: SSL certificate problem: self signed certificate\r\n\r\nSelf-signed certs aren't a problem. Maybe a warning perhaps, but not a problem. Why would a server admin need to rely on outside parties to verify an internal server is what it says it is?\r\n\r\nIt would seem to me that an override option should be available, preferably with the cert displayed for manual verification. After all, I trust my servers. :)\r\n\r\nNextcloud Snap 9.x on Ubuntu 16.04."}}
{"actor":{"display_login":"fishscene"}}