Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

david.edson

I vote for a work around for this issue.

Please offer a way to 'accept' a known server that I trust and will accept the risk of connection please.
martin

Re: I am having the same issue, trying to connect to WebDAV server on iPad with Textastic application

@david.edson: Do you refer to the Bug 2109? It hasn't been implemented yet. Vote for it, if you want it to happen.
david.edson

I am having the same issue, trying to connect to WebDAV server on iPad with Textastic application

Can you please tell me the magic way to 'allow' connections using the advanced RAW settings in WinSCP? I am prepared to accept the security bypass between my owned two nodes.
benjamint

Same problem

Hey,
I have the same problem. I use WinSCP to connect to a bitrix24.de drive. Is there any solution or workaround?
martin

Re: Digest challenge not supported

Thanks for your report.
WinSCP 5.21 indeed does not support legacy RFC 2069 Digest anymore.
What server are you connecting to that still uses it?
Vepavani

Digest challenge not supported

Hello
I'm trying to connect by WebDAV protocol in new version 5.21.1, but it's occuring an error.
When I used to connect in 5.19.6 there wasn't any problem

Below a part of log

5.21.1
. 2022-07-19 14:50:43.506 auth: Post-send (#0), code is 401 (want 401), WWW-Authenticate is Digest realm="xxxxxx", nonce="62d6eef35510d"
. 2022-07-19 14:50:43.506 auth: Got challenge (code 401).
. 2022-07-19 14:50:43.506 auth: Got 'Digest' challenge.
. 2022-07-19 14:50:43.506 auth: Trying Digest challenge...
. 2022-07-19 14:50:43.506 auth: No challenges accepted.
. 2022-07-19 14:50:43.506 Request ends, status 401 class 4xx, error line:
. 2022-07-19 14:50:43.506 Could not authenticate to server: legacy Digest challenge not supported
. 2022-07-19 14:50:43.506 Request ends.
. 2022-07-19 14:50:43.506 sess: Destroying session.
. 2022-07-19 14:50:43.506 sess: Closing connection.
. 2022-07-19 14:50:43.506 ssl: Shutdown state: not sent | not received.
. 2022-07-19 14:50:43.506 ssl: Sending closure.
. 2022-07-19 14:50:43.506 sess: Connection closed.
* 2022-07-19 14:50:43.527 (EFatal) Autenticação falhou.
* 2022-07-19 14:50:43.527 Could not authenticate to server: legacy Digest challenge not supported
* 2022-07-19 14:50:43.527 Conexão falhou.

5.19.6
. 2022-07-19 10:21:14.805 ah_post_send (#0), code is 401 (want 401), WWW-Authenticate is Digest realm="xxxxxx", nonce="62d6afca67a53"
. 2022-07-19 10:21:14.805 auth: Got challenge (code 401).
. 2022-07-19 10:21:14.805 auth: Got 'Digest' challenge.
. 2022-07-19 10:21:14.805 auth: Trying Digest challenge...
. 2022-07-19 10:21:14.805 Password prompt
. 2022-07-19 10:21:17.184 auth: H(A1) is [92e5ff06c69f37197db38f508fcddd0a]
. 2022-07-19 10:21:17.184 auth: Accepting digest challenge.
. 2022-07-19 10:21:17.184 auth: Accepted Digest challenge.
. 2022-07-19 10:21:17.184 auth: Sending 'Digest' response.
. 2022-07-19 10:21:17.184 auth: H(A2): 45209fdfa2194d3a36f665fac6935be6
. 2022-07-19 10:21:17.184 Sending request headers:
. 2022-07-19 10:21:17.184 OPTIONS /company/personal/user/2019/disk/path/ HTTP/1.1
. 2022-07-19 10:21:17.184 User-Agent: WinSCP/5.19.6 neon/0.31.2
. 2022-07-19 10:21:17.184 Keep-Alive:
. 2022-07-19 10:21:17.184 Connection: TE, Keep-Alive
. 2022-07-19 10:21:17.184 TE: trailers
. 2022-07-19 10:21:17.184 Host: xxxxxxxxx
. 2022-07-19 10:21:17.184 Authorization: