On Thu, Aug 1, 2013 at 7:22 PM, Ben Reser wrote:
> On Thu, Aug 1, 2013 at 7:04 PM, Brennan, Edward C (HII-Ingalls)
> wrote:
>> Thanks, Ben. So based on your response, I still don't know what caused the
>> error. I introduced apache 2.2.25 into my environment, and I get the error
>> (which is
On Thu, Aug 1, 2013 at 7:04 PM, Brennan, Edward C (HII-Ingalls)
wrote:
> Thanks, Ben. So based on your response, I still don't know what caused the
> error. I introduced apache 2.2.25 into my environment, and I get the error
> (which is why I posted to users@httpd, since I didn't introduce a n
52 PM
To: users@httpd.apache.org
Subject: EXT :Re: [users@httpd] RE: EXT :Re: [users@httpd] apache 2.2.25 and
svn commit
First of all this probably belongs on us...@subversion.apache.org...
On Wed, Jul 31, 2013 at 1:43 PM, Brennan, Edward C (HII-Ingalls)
wrote:
> Thank you.
> I am tryi
First of all this probably belongs on us...@subversion.apache.org...
On Wed, Jul 31, 2013 at 1:43 PM, Brennan, Edward C (HII-Ingalls)
wrote:
> Thank you.
> I am trying to understand what the recommendation is here. I am currently
> using SVN 1.6.6 and have apache 2.2.22 in production (reverte
Thank you.
I am trying to understand what the recommendation is here. I am currently
using SVN 1.6.6 and have apache 2.2.22 in production (reverted back from
2.2.25). At this link:
http://subversion.apache.org/security/CVE-2013-4131-advisory.txt
there is this blurb:
Making a copy of the
