Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client does not send client TLS certificate #6911

Closed
albatross0 opened this issue Dec 1, 2018 · 11 comments
Closed

Client does not send client TLS certificate #6911

albatross0 opened this issue Dec 1, 2018 · 11 comments
Assignees
Labels
Milestone

Comments

@albatross0
Copy link

Expected behaviour

A new account is created.

Actual behaviour

I tried to add a new account using the client TLS ceritificate but it failed.
(No client certificates in the TLS handshake packets)
Owncloud client version 2.5.0 does not have this problem.

Steps to reproduce

  1. Install owncloud client version 2.5.1
  2. Add a new account using the client TLS certificate

Client configuration

Client version: 2.5.1

Operating system: Windows 10

OS language: Japanese

Logs

  1. Client logfile: https://gist.github.com/albatross0/2758870f54f5edd935baaef981202b95
@guruz
Copy link
Contributor

guruz commented Dec 3, 2018

@albatross0 Which error message do you get when adding a NEW acccount (with same URL)?

@albatross0
Copy link
Author

Since my server requires a client TLS ceritificate, the connection failed for the first time and this dialog was displayed.

owncloud02

I selected the Configure client-side TLS ceritificate button and specified a certificate and password.

owncloud03

However, the Connection failed dialog was displayed again.

owncloud02

@guruz
Copy link
Contributor

guruz commented Dec 4, 2018

(No client certificates in the TLS handshake packets)

How did you find this out? Network sniffer?

Does the log on the server confirm this?

FYI @dschmidt you changed the SSL version in 2.5.1?

@albatross0
Copy link
Author

How did you find this out? Network sniffer?

Yes. I used Wireshark.

I think probably #6836 affects this issue.

@dschmidt
Copy link
Member

dschmidt commented Dec 5, 2018

FYI @dschmidt you changed the SSL version in 2.5.1?

I think so. From 1.1.0x to 1.1.1

@guruz
Copy link
Contributor

guruz commented Dec 29, 2018

Client version 2.5.1 (build 10818) Qt 5.10.1 SSL OpenSSL 1.1.1 11 Sep 2018
@dschmidt Did you check if Qt's OpenSSL 1.0 backend has feature parity with the old 1.0 OpenSSL backend before updating? AFAIK they're using different classes.

I spent 5 minutes to search on https://bugreports.qt.io/secure/Dashboard.jspa but didnt see anything

@guruz guruz added this to the 2.5.x milestone Jan 11, 2019
@guruz guruz changed the title Client does not send client TLS certificate [macOS] Client does not send client TLS certificate Jan 11, 2019
@ckamm
Copy link
Contributor

ckamm commented Jan 11, 2019

Could be related to ef99800 which is in 2.5.1.
Edit: Yes, the cert and private key gets added to the config in OwncloudSetupPage::slotCertificateAccepted() but is wiped there.
Edit: Hmm, if it's called again that is. Maybe not.

@ckamm ckamm changed the title [macOS] Client does not send client TLS certificate Client does not send client TLS certificate Jan 11, 2019
@ckamm ckamm assigned ckamm and unassigned guruz Jan 11, 2019
@ckamm ckamm added type:bug and removed Needs info labels Jan 11, 2019
@guruz guruz added ReadyToTest QA, please validate the fix/enhancement and removed PR available labels Jan 14, 2019
@guruz
Copy link
Contributor

guruz commented Jan 17, 2019

@albatross0 Do you want to test the rc2 which contains a fix for this?
https://download.owncloud.com/desktop/testing/ownCloud-2.5.2.11335.11186-rc2.en-US.msi

@albatross0
Copy link
Author

@guruz Thank you for letting me know.
It works properly in my environment.

@guruz
Copy link
Contributor

guruz commented Jan 18, 2019

@albatross0 great:)

@guruz guruz closed this as completed Jan 18, 2019
@jnweiger
Copy link
Contributor

tested 252rc2

issue-owner confirmed ,it works fine

@jnweiger jnweiger removed the ReadyToTest QA, please validate the fix/enhancement label Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants