GothenburgBitFactory/taskwarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/taskwarrior.git synced 2025-08-21 07:43:08 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Documentation

Browse source 
- Added man page updates to reflect new 'taskd.trust' settings.
This commit is contained in:
Paul Beckingham 2014-04-05 12:13:02 -04:00
parent 6354bc09ab
commit 620f9b40b2
2 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
NEWS
View file

@ -13,6 +13,8 @@ New commands in taskwarrior 2.4.0
New configuration options in taskwarrior 2.4.0 New configuration options in taskwarrior 2.4.0
- The 'taskd.trust' setting is now a tri-state, supporting values 'strict',
'ignore hostname' and 'allow all', for server certificate validation.
- New themes: dark-default-16.theme, dark-gray-blue-256.theme - New themes: dark-default-16.theme, dark-gray-blue-256.theme
Newly deprecated features in taskwarrior 2.4.0 Newly deprecated features in taskwarrior 2.4.0

10
doc/man/taskrc.5.in
View file

@ -1358,11 +1358,13 @@ using a self-signed certificate. Optional.
.RE .RE
.TP .TP
.B taskd.trust=yes|no .B taskd.trust=strict|ignore hostname|allow all
.RS .RS
If you do not specify a CA certificate when your Taskserver is using a self- This settings allows you to override the trust level when server certificates
signed certificate, you can override the certificate validation by setting this are validated. With "allow all", the server certificate is trusted
value to 'yes'. Default is not to trust a server certificate. automatically. With "ignore hostname", the server certificate is verified but
the hostname is ignored. With "strict", the server certificate is verified.
Default is "strict", which requires full validation.
.RE .RE
.TP .TP