-
Notifications
You must be signed in to change notification settings - Fork 46
Connection-0.2.6 breaks Amazonka (stackage lts-6.12 on up) #23
Comments
lts-6.11 completes without error for my project
|
Sorry for your hair ! |
My hair is ok :) Here's a script that will reproduce
Run it against any AWS account with some buckets & objects. After about 30 seconds or so it'll crash. |
change the script to lts-6.11 and it'll work fine |
I wonder if this is related to erikd-ambiata/test-warp-wai#1 (comment) ? |
Looks similar @erikd |
dysinger: I'm not sure how to test this script with a non-released version of cryptonite, any idea ? |
I've tried recreating my issue just using the connection library talking to HTTP and HTTPS servers. Was not able to find anything, suggesting that this was actually a problem with http-client. |
@erikd: I don't think that's the case, definitely a low level crypto issue. did you use the git version of cryptonite ? |
Nope, used the 0.19 release version. |
Ah ok, may be a different issue. |
is this still a bug ? (both connection and tls has new revisions since) |
Its still a I can test again (tomorrow) if you let me know what versions I should be testing. |
that sounds like a different bug from the BadRecordMac |
Opened #29 . |
I tracked this down over the last full day of pulling my hair. It was not unlike the bug seen in hs-tls 1.3.4 where you would get bad mac every once in a while.
With connection-0.2.5 I can pound away on amazonka. With connection-0.2.6 I get random bad mac errors.
The text was updated successfully, but these errors were encountered: