jenkinsci / jenkinsci/subversion-plugin

[JENKINS-13762] Subversion authentication module doesn't handle invalid cert file or wrong cert password for https-client-certificates correctly

Open
#918 1 comment 0 reactions 0 assignees View on GitHub
component:subversion-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
131
Forks
275
Avg merge
12h 4m
Merged PRs (30d)
6

Description

The subversion authentication module accepts any file as certificate and anything as password. A failure always results in the same not helpful exception "SSL handshake failed: 'Received fatal alert: handshake_failure'" after the subversion client send a empty client certificate send to the server on the TLS connection. I am not sure if is allowed to send a empty client certificate message to the server.

Due the complexity of the software chain and configuration parameters used for HTTPS authentication, it is very annoying to find the real problem if no component returns a usable error message.

The expected behavior is to validate the input parameters and do not try to establish a connection with obvious invalid parameters.

---
Originally reported by mborm, imported from: Subversion authentication module doesn't handle invalid cert file or wrong cert password for https-client-certificates correctly


  • status: Open
  • priority: Major
  • component(s): subversion-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 0
  • imported: 20251212-090250

Raw content of original issue

The subversion authentication module accepts any file as certificate and anything as password. A failure always results in the same not helpful exception "SSL handshake failed: 'Received fatal alert: handshake_failure'" after the subversion client send a empty client certificate send to the server on the TLS connection. I am not sure if is allowed to send a empty client certificate message to the server.

Due the complexity of the software chain and configuration parameters used for HTTPS authentication, it is very annoying to find the real problem if no component returns a usable error message.

The expected behavior is to validate the input parameters and do not try to establish a connection with obvious invalid parameters.

  • environment: Windows Server 2003, Java 1.6.0.31, Jenkins 1.463, Subversion Plugin 1.39

2 attachments

- [emptycertificate.png](https://issues.jenkins.io/secure/attachment/21818/emptycertificate.png)
> ![emptycertificate.png](https://issues.jenkins.io/secure/attachment/21818/emptycertificate.png)
- [subversionException.txt](https://issues.jenkins.io/secure/attachment/21817/subversionException.txt)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.