-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS Illegal_parameter
on macOS
#478
Comments
Doe the mirage-crypto-ec test suite run fine on your machine? Would be great if you could test the same version of mirage-crypto as you're using when compiling tls. My feat is that this is another occurence of mit-plv/fiat-crypto#1606 (comment) -- i.e. a bad C compiler (14.0.3) on macOS that does bad optimizations on arm64. I'm slightly confused that you mention "cohttp-lwt-eio" in your inital message, but the samepl code and package versions include only cohttp-lwt-unix. But that shouldn't make any difference. |
Tried the EC tests and they fail on my machine, so I think your inclination is correct :(
It was only mentioned because the original gist used |
…age, mirage-crypto-rng-lwt, mirage-crypto-rng-eio, mirage-crypto-rng-async, mirage-crypto-pk and mirage-crypto-ec (0.11.2) CHANGES: * mirage-crypto-rng-eio: improve portability by using eio 0.7's monotonic clock interface instead of mtime.clock.os. (mirage/mirage-crypto#176 @TheLortex) * mirage-crypto-rng-eio: update to eio 0.12 (mirage/mirage-crypto#182 @talex5) * mirage-crypto-rng: fix typo in RNG setup (mirage/mirage-crypto#179 @samueldurantes) * macOS: on arm64 with clang 14.0.3, avoid instcombine (due to miscompilations) reported by @samoht mit-plv/fiat-crypto#1606 (comment) re-reported in ulrikstrid/ocaml-jose#63 and mirleft/ocaml-tls#478 (mirage/mirage-crypto#185 @hannesm @kit-ty-kate) * avoid "stringop-overflow" warning on PPC64 and S390x (spurious warnings) when in devel mode (mirage/mirage-crypto#178 mirage/mirage-crypto#184 @avsm @hannesm) * stricter C prototypes, unsigned/signed integers (mirage/mirage-crypto#175 @MisterDA @haesbaert @avsm @hannesm) * support DragonFlyBSD (mirage/mirage-crypto#181 @movepointsolutions) * support GNU/Hurd (mirage/mirage-crypto#174 @pinotree)
please try mirage-crypto-ec at 0.11.2, as PRed to opam-repository ocaml/opam-repository#24461 |
…age, mirage-crypto-rng-lwt, mirage-crypto-rng-eio, mirage-crypto-rng-async, mirage-crypto-pk and mirage-crypto-ec (0.11.2) CHANGES: * mirage-crypto-rng-eio: improve portability by using eio 0.7's monotonic clock interface instead of mtime.clock.os. (mirage/mirage-crypto#176 @TheLortex) * mirage-crypto-rng-eio: update to eio 0.12 (mirage/mirage-crypto#182 @talex5) * mirage-crypto-rng: fix typo in RNG setup (mirage/mirage-crypto#179 @samueldurantes) * macOS: on arm64 with clang 14.0.3, avoid instcombine (due to miscompilations) reported by @samoht mit-plv/fiat-crypto#1606 (comment) re-reported in ulrikstrid/ocaml-jose#63 and mirleft/ocaml-tls#478 (mirage/mirage-crypto#185 @hannesm @kit-ty-kate) * avoid "stringop-overflow" warning on PPC64 and S390x (spurious warnings) when in devel mode (mirage/mirage-crypto#178 mirage/mirage-crypto#184 @avsm @hannesm) * stricter C prototypes, unsigned/signed integers (mirage/mirage-crypto#175 @MisterDA @haesbaert @avsm @hannesm) * support DragonFlyBSD (mirage/mirage-crypto#181 @movepointsolutions) * support GNU/Hurd (mirage/mirage-crypto#174 @pinotree)
Hello! Thank you for the great library.
On the OCaml discord someone mentioned having issues with tls-eio and making a GET request with cohttp-eio (see the #webdev channel). They linked this example https://gist.github.com/specialblend/90c074fa7c5ebc24a29239c4ccbc983a. I tried it and also got the same error. Trying it on a linux machine however did not reproduce the error. I tried the example using the Lwt stack and saw the same thing. A smaller repro is:
Debug log output
On Linux the debug log shows more or less the same thing but it continues past this point.
Package Versions
0.17.1
0.17.1
5.3.0
Hopefully I'm just doing something wrong, do let me know if I can help in any way.
The text was updated successfully, but these errors were encountered: