Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WWW-25] Change documentation to include Let's Encrypt certificate usage #31

Open
taskwarrior opened this issue Feb 12, 2018 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@taskwarrior
Copy link
Contributor

MG on 2017-12-20T14:08:33Z says:

Implementation of Let's Encrypt certificates for outbound server connection is possible. There are multiple reported instances. Please add instructions to documentations.
Compare for example [https://answers.tasktools.org/questions/5439720/answers/7241971] or [https://gist.github.com/polettix/e8007a7f2064e7f133d93e060032a880]

 

Changes on taskd server config:

server.cert=/path/to/letsencrypt-certificate-server.cert.pem

server.key=/path/to/letsencrypt-certificate-server.key.pem

Changes on taskwarrior client config:

taskd.ca=[Let's Encrypt X3 Intermediate certificate].pem (available at https://letsencrypt.org/certificates/)

 

Remaining configuration and setup stays the same. Depending on setup it could be good practise to link LE certificates in $TASKDATA (ln -sf) instead of directly referring them in config.

 

@taskwarrior taskwarrior added this to the Backlog milestone Feb 12, 2018
@taskwarrior taskwarrior added the enhancement New feature or request label Feb 12, 2018
@taskwarrior
Copy link
Contributor Author

Migrated metadata:

Created: 2017-12-20T14:08:33Z
Modified: 2018-01-09T14:05:05Z

@taskwarrior
Copy link
Contributor Author

Paul Beckingham on 2018-01-09T14:05:05Z says:

This is going in the FAQ, which will be online soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant