RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
evolution/e-d-s/libsoup/gnults can't connect to TLSv1-only caldav server because it specified version 3 (0x0300) in ClientHello. According to RFCs, latest TLS version supported by client should be specified in client hellos, for which GnuTLS provides convenient %LATEST_RECORD_VERSION keyword:
http://gnutls.org/manual/gnutls.html#tab_003aprio_002dspecial1

The bug might easily be in lower layers (libsoup) as wel...

Version-Release number of selected component (if applicable):
evolution-2.32.3-9.el6.x86_64
evolution-data-server-2.32.3-7.el6.x86_64
libsoup-2.28.2-4.el6.x86_64
gnutls-2.8.5-10.el6_4.2.x86_64

How reproducible:
always

Steps to Reproduce:
1. create a new caldav calendar in evolution:
  - use any uri on https server that supports only TLSv1 or better
  - check "Use SSL"
2. start network capture on port 443
3. hit "Browser server to discover calendar" button

Actual results:
* version in ClientHello handshake is SSL 3.0 (0x0300)
* connection is refused

Expected results:
* version in ClientHello is highest supported by client
* connection is established

Additional info:
My server supports just TLSv1 (apache + mod_nss: TLS 1.1 and 1.2 aren't supported yet and I disabled SSLv3 support)

The issue is the same when using nautilus to connect to the same server via webdav, thust I expect that the problematic component is actually libsoup.
nautilus-2.28.4-19.el6.x86_64
gvfs-1.4.3-15.el6.x86_64

This is bug #975457, from my point of view.

yes, this is exactly the same bug as 975457

Thanks for the confirmation, I'm marking it as such.

*** This bug has been marked as a duplicate of bug 975457 ***