Kong / Kong/insomnia

SSL routine error - Client Certificate Auth

Open
#7,066 0 comments 0 reactions 0 assignees View on GitHub
B-bug S-unverified
Dominant language
TypeScript
Stars
40k
Forks
2.4k
Avg merge
2d 13h
Merged PRs (30d)
61

Description

### Expected Behavior

I would expect that the SSL libraries could be configured to work with older certificates where it is not possible to Upgrade.

### Actual Behavior

> User-Agent: insomnia/8.6.0
> Proxy-Connection: Keep-Alive

< HTTP/1.1 200 Connection established

* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
* could not load PEM client certificate, OpenSSL error error:0A00018E:SSL routines::ca md too weak, (no key found, wrong pass phrase, or wrong file format?)
* Closing connection 12

### Reproduction Steps

_No response_

### Is there an existing issue for this?

- [X] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.

### Additional Information

In other platforms (linux) can put in a configuration option in the openssl.cnf file to permit the connections

e.g.

[system_default_sect]
CipherString = DEFAULT:@SECLEVEL=0

However, there appears to be no options for the same to be done on Windows with the libraries being used, is there a way that this can be a work around for this?

### Insomnia Version

Insomnia Core 8.6.0

### What operating system are you using?

Windows

### Operating System Version

Win 10 Ent

### Installation method

Running insomnia core

### Last Known Working Insomnia version

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue identifies Windows 10, Insomnia Core 8.6.0, client-certificate authentication, and an OpenSSL “ca md too weak” error, but names no files or tests and provides no reproduction steps. Start by locating the Windows TLS client-certificate setup and how OpenSSL security settings are supplied; done means a supported workaround or configuration is identified and verified for this failure.

Written by the indexing model from the issue text.

Assessment

Domain
networking, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.