`curl --insecure` doesn't work with cvm-proxy server
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- backend, networking
Research direction
Start by reproducing curl --insecure <cvm_proxy_url> and inspect the cvm-proxy TLS handshake path. Compare the client-side TLS alert with the server's illegal base64 error; done means the request succeeds with --insecure without that handshake error, while the existing verification scripts continue to work.
Written by the indexing model from the issue text.
Description
When trying to use curl --insecure <cvm_proxy_url>, it's returning errors.
On the curl client side:
curl: (35) error:0A000438:SSL routines::tlsv1 alert internal error
On the cvm-proxy server side:
http: TLS handshake error from 95.94.96.182:34856: illegal base64 data at input byte 10
Not critical as the main verification scripts still work, see also https://buildernet.org/docs/send-orderflow#tee-attestation
But might be worth investigating, and if i recall correctly it did work in the past 🤔
- Dominant language
- Go
- Stars
- 16
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·