From: Simon <turner25@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: SSL giving corrupted MAC on input
Date: Mon, 6 Jul 2009 12:43:59 -0400 [thread overview]
Message-ID: <5f14cf5e0907060943l209f5549rd94409b99f2ae6b7@mail.gmail.com> (raw)
In-Reply-To: <5f14cf5e0907060931l2b59bc8pc0c53e6c3a569790@mail.gmail.com>
> A quick troubleshooting i've done was to setup apache and simply
> wget a very large file over plain HTTP. Transfer worked, i did it a
> second time and diff'ed the two downloads, they were the same. I then
> did the same test over HTTPS and got an error
> (SSL3_GET_RECORD:decryption failed or bad record mac). This clarified
> the problem is much more related to SSL than anything else.
Forgot to mention, i'm connecting to the machine via ssh and never get
disconnected, ssh terminal works perfectly fine, but anything going
through ssh for large transfers fails (ie rsync, unison, etc).
next prev parent reply other threads:[~2009-07-06 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 16:31 [gentoo-user] SSL giving corrupted MAC on input Simon
2009-07-06 16:43 ` Simon [this message]
2009-07-07 0:47 ` Paul Colquhoun
2009-07-20 18:59 ` Simon
2009-07-20 19:16 ` Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f14cf5e0907060943l209f5549rd94409b99f2ae6b7@mail.gmail.com \
--to=turner25@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox