cryptoadvance / cryptoadvance/specter-desktop
Bug: SSL and Chromium freezes Specter
- Dominant language
- Python
- Stars
- 847
- Forks
- 259
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 2
Description
**Describe the bug**
Specter website does not load in any browser after it has been tried by Chromium. Chromium seems to be able to completely block specter from reacting for anyone, when using ssl.
Chromioum gives the error (in console)
```
CertVerifyProcBuiltin for localhost failed:
----- Certificate i=0 (CN=Specter Citadel Cert,OU=Specter Citadel Cert,O=Specter Citadel Cert,L=Freiburg,ST=BDW,C=DE) -----
ERROR: No matching issuer found
handshake failed; returned -1, SSL error code 1, net_error -202
```
**To Reproduce**
Steps to reproduce the behavior:
1. Start specter with ssl `python3 setup.py install && python3 -m cryptoadvance.specter server --config DevelopmentConfig --host 0.0.0.0 --port 1234 --debug --ssl`
2. Access Specter in Chromium . --> This will not load (I think Chromium has some issue with self-signed certificates). Without SSL, Chromium loads normally and there is also no blocking of the server.
3. Access in a parallel window in Firefox also Specter. This then also will not load. This issue seems to have no timeout, and a server restart is needed.
**Expected behavior**
Even if a browser (like Chromium) causes some issues with specter and does not load, it should not block the server completely.
**Desktop (please complete the following information):**
- linux, ubuntu
- Firefox 103.0.1 (64-bit)
- Chromium Version 104.0.5112.79 (Official Build) snap (64-bit)
- Specter Version: master 802fe902dd4d3ff01d1cd6295934bf2658221e19
Contributor guide
Research direction
Start the server with the documented Python command using --ssl, then reproduce the Chromium certificate error and compare behavior in Firefox. No files or tests are named; trace the SSL request handling to determine why one failed browser connection blocks the server, and confirm that the server remains responsive afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100