Date: Wed, 22 Jan 2014 15:59:24 GMT From: titus m <titus@edc.ro> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/186004: svnup bugs Message-ID: <201401221559.s0MFxO4h020331@oldred.freebsd.org> Resent-Message-ID: <201401221600.s0MG00n0098753@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 186004 >Category: ports >Synopsis: svnup bugs >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 22 16:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: titus m >Release: 10.0-RELEASE >Organization: edc >Environment: FreeBSD fbsd10 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: 1. svnup crashes with ssl protocol svn0.eu.FreeBSD.org seems to be fine on us servers 2. svnup / http does not work thru / crashes transparent proxy (squid) the problem seems to be caused of the chunked encoding re-served by squid original content seems to always have chunks aligned to a newline boundary and the squid served one does not so the content may look like <taCHUNKSIZE\r\ng attrib="value">tag contents</tag> this causes the parse_xml function to return null values (which are never checked) >How-To-Repeat: 1. connect via ssl to svn0.eu.FreeBSD.org on 10.0-RELEASE (bombs in SSL_connect) 2. use svnup via transparent squid (3.2.x tested) this probably bombs on any version 32/64 freebsd 8/9/10 etc >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201401221559.s0MFxO4h020331>