0013354: Broken Windows WebDAV-Client affects all dotNET-applications #6606

Open
Gloirin opened this Issue Jun 9, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@Gloirin

Gloirin commented Jun 9, 2018

Reported by lab-at-nohl on 24 Jul 2017 00:06

Version: git master

This is related to #0012614 for which I provided a patch. It turned out that other Windows clients than Explorer (i.e. Duplicati) doesn't work either.

Additionally, user estradis pointed out a flaw for the previous patch (already in master).

ToDo:

  • make patch independent of specific user agent
  • only react to empty PROPFIND requests (others may be empty files)

I will send a pull request.

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by mspahn on 14 Aug 2017 08:44

I found another flaw here. The webdav client in windows sends an options request. This options request is rejected by the authentication layer in Tine 2.0. Know clue for how long that happens.

Tine 2.0 needs to handle those options request properly. We need to check the protocol spec. Or if you like you are welcome of course!

Gloirin commented Jun 11, 2018

Comment posted by mspahn on 14 Aug 2017 08:44

I found another flaw here. The webdav client in windows sends an options request. This options request is rejected by the authentication layer in Tine 2.0. Know clue for how long that happens.

Tine 2.0 needs to handle those options request properly. We need to check the protocol spec. Or if you like you are welcome of course!

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by pschuele on 14 Sep 2017 07:54

just merged #25

@mspahn: does it fix the OPTIONS problem?

Gloirin commented Jun 11, 2018

Comment posted by pschuele on 14 Sep 2017 07:54

just merged #25

@mspahn: does it fix the OPTIONS problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment