Re: Possible bug: Bad record MAC

2013-03-05 Thread Paolo Cavallini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 05/03/2013 23:12, Philip Martin ha scritto: >> Il 05/03/2013 14:09, Philip Martin ha scritto: >> >>> You don't say which client/OS you are using or which http >>> library the Subversion client is using. >> >> subversion 1.6.17dfsg-4 openssl 1.0.1e

Re: Possible bug: Bad record MAC

2013-03-05 Thread Daniel Shahaf
Philip Martin wrote on Tue, Mar 05, 2013 at 22:12:17 +: > Paolo Cavallini writes: > > Network has bben checked cables and switch have been changed, firewall > > and proxy have not changed. > > So it could be a communication problem between openssl and subversion. > > > > Any hint on how to deb

Re: Possible bug: Bad record MAC

2013-03-05 Thread Philip Martin
Paolo Cavallini writes: > Hi Philip, > thanks for your reply. > > Il 05/03/2013 14:09, Philip Martin ha scritto: > >> You don't say which client/OS you are using or which http library >> the Subversion client is using. > > subversion 1.6.17dfsg-4 > openssl 1.0.1e-1 > on debian testing, up to date

Re: Possible bug: Bad record MAC

2013-03-05 Thread Paolo Cavallini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Philip, thanks for your reply. Il 05/03/2013 14:09, Philip Martin ha scritto: > You don't say which client/OS you are using or which http library > the Subversion client is using. subversion 1.6.17dfsg-4 openssl 1.0.1e-1 on debian testing, up to

Re: Possible bug: Bad record MAC

2013-03-05 Thread Philip Martin
Paolo Cavallini writes: > I'm consistently getting this error when svn up or ci: > > Could not read status line: SSL alert received: Bad record MAC > > Unsure whether it's an svn problem, or a network one. I've checked > with my server hosting, and thay say it's software, but I cannot find > a r

Possible bug: Bad record MAC

2013-03-03 Thread Paolo Cavallini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. I'm consistently getting this error when svn up or ci: Could not read status line: SSL alert received: Bad record MAC Unsure whether it's an svn problem, or a network one. I've checked with my server hosting, and thay say it's software, but