☰

Curl은 "SSL 루틴: ssl3_read_bytes: sslv3 경고 핸드셰이크 실패"를 제공합니다.

tag-icon • tag-icon debian ubuntu curl
Curl은 "SSL 루틴: ssl3_read_bytes: sslv3 경고 핸드셰이크 실패"를 제공합니다.

컬을 실행 https://www.ethics.state.tx.us/data/search/lobby/TEC_LA_CSV.zip하면

error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

온라인에서 본 다른 내용을 추가해 보았지만 아무 것도 작동하지 않는 것 -2같습니다 . -3이 문제를 해결하고 컬을 사용하여 이 파일을 다운로드하려면 어떻게 해야 합니까?

이것은 아래 컬의 출력입니다.

$ curl -vvvk "https://www.ethics.state.tx.us/data/search/lobby/TEC_LA_CSV.zip"
*   Trying 204.65.203.80:443...
* TCP_NODELAY set
* Connected to www.ethics.state.tx.us (204.65.203.80) 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 alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

를 사용하려고 할 때도 이것을 보았습니다 -2.

curl: (4) OpenSSL was built without SSLv2 support

그리고-3

curl: (4) OpenSSL was built without SSLv3 support

답변1

나는 매우 비밀스러운 Debian/Ubuntu를 사용해야 했습니다.--ciphers DEFAULT@SECLEVEL=1

$ curl --ciphers DEFAULT@SECLEVEL=1 -vvvk "https://www.ethics.state.tx.us/data/search/lobby/TEC_LA_CSV.zip"

우리의 경우 이는 TLS1.2, AES128-GCM-SHA256의 협상을 가능하게 합니다.

* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / AES128-GCM-SHA256
* ALPN, server did not agree to a protocol

irc://irc.freenode.net/#curl에서 검색함

01:40 < bagder> EvanCarroll: add "--ciphers DEFAULT@SECLEVEL=1"
01:41 < EvanCarroll> zomfg.
01:41 < EvanCarroll> Where is that documented.
01:41 < EvanCarroll> nice trick.
01:42 < bagder> that's debian (ubuntu?) making things hard for users by upping that seclevel in the openssl conf
01:42 < bagder> and openssl gives a crappy error message there too, not helping either

관련 정보