| commit | 3d11a61242e1a65a7dcdcea28d878ca5574c46bf | |
| author | Stefan Becker <chemobejk@gmail.com> | |
| Sun, 3 Mar 2013 11:39:34 +0000 (3 13:39 +0200) | ||
| committer | Stefan Becker <chemobejk@gmail.com> | |
| Sun, 3 Mar 2013 11:39:34 +0000 (3 13:39 +0200) | ||
| tree | 5e127b571e0214af2ce96f83679e93b2e41efd11 | treesnapshot (tar.gz zip) |
| parent | 9d6da89be958ed5f5ed3c6b2b26339de36d71bd3 | commitdiff |
tls-dsk: allow password-less configurations
If SSPI or Kerberos are compiled in then it is possible that all HTTP
authentication to publish the TLS-DSK client certificate can be done
using Single Sign-On. Therefore we TLS-DSK should not be hard-coded to
always require a password.
If SSPI or Kerberos are compiled in then it is possible that all HTTP
authentication to publish the TLS-DSK client certificate can be done
using Single Sign-On. Therefore we TLS-DSK should not be hard-coded to
always require a password.
| ChangeLog | diffblobblamehistory | |
| src/core/sip-sec-tls-dsk.c | diffblobblamehistory |