blob: 72fd151f9c555910036e1a8ad5286c029404825e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
Curl/OpenSSL failure
```
./Bin/ELFLoader -T 1 -U -c irint -n 500 -- `which curl` -v -H -GET https://google.com
```
This gives a fairly bad output.
```
* Trying 172.217.164.110:443...
* TCP_NODELAY set
* Connected to google.com (172.217.164.110) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (OUT), TLS alert, bad certificate (554):
* error:1012606B:elliptic curve routines:EC_POINT_set_affine_coordinates:point is not on curve
* Closing connection 0
curl: (35) error:1012606B:elliptic curve routines:EC_POINT_set_affine_coordinates:point is not on curve
```
This failure point is in openssl. One can build their unit tests and run the `ectest` unit test to see the failure.
Looks like it could be a failure in their BIGNUM implementation but more testing needs to be done.
|