Please describe the current behavior, and explain why it's bad.
It looks like Tusk uses only basic auth for WebDAV. I set up a WebDAV share, I validated that it worked with my Tusk user ID/pass using another WebDAV client. When I use the same URL, ID, and password with Tusk, my Apache error log says "client used wrong authentication scheme `Basic': /tusk/"
Please describe how you think it should change.
I really don't want to be sending my WebDAV credentials in basic auth on http (and yes, it would only be my tusk WebDAV, but security is a multi-layered thing).
This issue is a
Please describe the current behavior, and explain why it's bad.
It looks like Tusk uses only basic auth for WebDAV. I set up a WebDAV share, I validated that it worked with my Tusk user ID/pass using another WebDAV client. When I use the same URL, ID, and password with Tusk, my Apache error log says "client used wrong authentication scheme `Basic': /tusk/"
Please describe how you think it should change.
I really don't want to be sending my WebDAV credentials in basic auth on http (and yes, it would only be my tusk WebDAV, but security is a multi-layered thing).
Anything else?