{"action":"closed","issue":{"url":"https://api.github.com/repos/diafygi/acme-tiny/issues/77","repository_url":"https://api.github.com/repos/diafygi/acme-tiny","labels_url":"https://api.github.com/repos/diafygi/acme-tiny/issues/77/labels{/name}","comments_url":"https://api.github.com/repos/diafygi/acme-tiny/issues/77/comments","events_url":"https://api.github.com/repos/diafygi/acme-tiny/issues/77/events","html_url":"https://github.com/diafygi/acme-tiny/issues/77","id":128894155,"number":77,"title":"Dump intermediate certificate","user":{"login":"PhrozenByte","id":920356,"avatar_url":"https://avatars.githubusercontent.com/u/920356?v=3","gravatar_id":"","url":"https://api.github.com/users/PhrozenByte","html_url":"https://github.com/PhrozenByte","followers_url":"https://api.github.com/users/PhrozenByte/followers","following_url":"https://api.github.com/users/PhrozenByte/following{/other_user}","gists_url":"https://api.github.com/users/PhrozenByte/gists{/gist_id}","starred_url":"https://api.github.com/users/PhrozenByte/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PhrozenByte/subscriptions","organizations_url":"https://api.github.com/users/PhrozenByte/orgs","repos_url":"https://api.github.com/users/PhrozenByte/repos","events_url":"https://api.github.com/users/PhrozenByte/events{/privacy}","received_events_url":"https://api.github.com/users/PhrozenByte/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2016-01-26T17:57:55Z","updated_at":"2016-02-22T22:27:39Z","closed_at":"2016-02-22T22:27:39Z","body":"Let's Encrypt doesn't guarantee the use of a specific intermediate certificate for signing. Therefore it's currently not possible for a user of `acme-tiny` to create a `chain.pem` and `fullchain.pem` without the risk of breaking his setup when Let's Encrypt (suddenly) switches to `Let’s Encrypt Authority X2`. To solve this problem, [a ACME server must send a `Link: <https://example.com/acme/ca-cert>;rel=\"up\";title=\"issuer\"` header](https://letsencrypt.github.io/acme-spec/#rfc.section.6.6.p.9) when [retrieving a signed certificate](https://github.com/diafygi/acme-tiny/blob/fcb7cd6f66e951eeae76ff2f48d8ad3e40da37ef/acme_tiny.py#L156).\r\n\r\nA possible solution I can think of is, that `acme-tiny` follows this link, appends all intermediate certificates to the signed certificate and therefore actually outputs/returns a `fullchain.pem`."}}