Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 292EE200BA7 for ; Fri, 7 Oct 2016 03:15:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 27C8E160AE0; Fri, 7 Oct 2016 01:15:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 44D2A160ADB for ; Fri, 7 Oct 2016 03:15:45 +0200 (CEST) Received: (qmail 94795 invoked by uid 500); 7 Oct 2016 01:15:44 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Delivered-To: moderator for users@subversion.apache.org Received: (qmail 92741 invoked by uid 99); 6 Oct 2016 14:41:23 -0000 X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.679 X-Spam-Level: * X-Spam-Status: No, score=1.679 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=HAbadisXXf2q4rwW8FXaTS/nxIQBAnA0d9JshPYxVRA=; b=tJij+F/XEkx3N5IrNur/FraJn4DB+0HuQ2hTiU8R05KpLHjEE1dqt+orUfsGGWJLiM o8OCj8UTQh5bdM8Y8JD1GGEzwJtIAtjQXHRVUH3gFu+/s1PhXLNZYCMUsBZUdDd07cYi 9ugrY+F9iYCeKUeYPIbNMh8GMUy59lkHlMr8jK8snHHbWpH8AkeTTwrqHAsBA55bkO78 CH6PnEQNE0CI2CPrI802Mchlo6RLRqd7IdCTlIfUxErIFFOcmMY2ui5R3Wo16GLgQ5mL E0o6pPQPxIjNmrXq/5D1MqPpZo7Z6J/hU+jlD3dKOQe3gwdgsFK2EmD4h38gjerIb2eu uqXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HAbadisXXf2q4rwW8FXaTS/nxIQBAnA0d9JshPYxVRA=; b=T2gRRHrF04vYu3PdihxKBvCXPrLUa40ZhlgTdwPzDtv4yv4kZUliVNWKXuj/Rf+FUY EPXlzV84gyVUuuw6lMpb6vNmrcDFvxYFPHG9l6WrJWwIVt2OvWfIfIIVZDE0R/bFYBIp PLstkI/Xg0usXguIkypNak1Lb4CYegIW9g639tFFu2UUjg9S/fF+jb4UTe88s8Iv1NXi gENNlfWk2IxFFcQEwlQn95+SmkneqUrbJfOUXvskzA5hRkyEVB0abae/Xw0sGLXPxgCm Rz6mtz4lc4JYDGvtlNxIeI96qk4clQxvZVkaFY9ig5wJkU5R6/Te3INg8FH65Xn+fWmW Xrsg== X-Gm-Message-State: AA6/9RlUvQz+NL91/dgAiBYVFH4BbK5izWVkR8NolINEUjn4EF3h9PM7T2ik4oJpMIEKAIhPdW03wa/hPfOBzQ== X-Received: by 10.36.149.193 with SMTP id m184mr32727876itd.94.1475764874963; Thu, 06 Oct 2016 07:41:14 -0700 (PDT) MIME-Version: 1.0 From: Tyler Smith Date: Thu, 6 Oct 2016 08:40:54 -0600 Message-ID: Subject: Reauthentication required when issuing a lock on multiple files To: users@subversion.apache.org Content-Type: multipart/alternative; boundary=94eb2c08b3c424f1e4053e334964 archived-at: Fri, 07 Oct 2016 01:15:46 -0000 --94eb2c08b3c424f1e4053e334964 Content-Type: text/plain; charset=UTF-8 Hello all, svn client: version 1.9.4 (r1740329) svn server: version 1.9.4 (r1740329), hosted on an Apache/2.4.6 (CentOS) server. I am experiencing an issue when running an svn lock command on multiple files where it will require me to enter authentication n-1 times where n is the number of files I am requesting a lock for. If I request a single lock, it will execute successfully without prompting for my password, having saved it previously. If I request more than one lock, it will first request my password, seeming to remember my username. However, for every additional file beyond 2, it will ask for my username as well as my password. c:\path\to\repo>svn lock file1.c file2.c file3.c Authentication realm: Subversion Repository Password for 'tylersmith': ********** Authentication realm: Subversion Repository Username: ** tylersmith Password for 'tylersmith': ********** 'file1.c' locked by user 'tylersmith'. 'file2.c' locked by user 'tylersmith'. 'file3.c' locked by user 'tylersmith'. I set up a test SVN server to support both http:// access as well as svn://. This problem does not occur with svn://. (If this issue is a lost cause via http://, I might consider switching if I can get around the username-password data for svnserve being contained in a plain text file.) Looking at a Wireshark trace of the initial command, I get two packets stating "401 Unauthorized". It is at this point that I am prompted by the command line client for my password(s). Only after entering all requested information does it send/receive more packets to/from the SVN server to complete the action. Is this an issue in the svn client or a but in the web authentication of the server? Thank you for your help, Tyler Smith --94eb2c08b3c424f1e4053e334964 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello all,

svn client: version 1.9.4 (r= 1740329)
svn server: version 1.9.4 (r1740329), hosted on an Apach= e/2.4.6 (CentOS) server.

I am experiencing an issue = when running an svn lock command on multiple files where it will require me= to enter authentication n-1 times where n is the number of files I am requ= esting a lock for.

If I request a single lock, it = will execute successfully without prompting for my password, having saved i= t previously.

If I request more than one lock, it = will first request my password, seeming to remember my username. However, f= or every additional file beyond 2, it will ask for my username as well as m= y password.

c:\path\to\repo>svn lock file1.c file2.c file3.c
Authentication realm: &l= t;http://svn.server.address:80= > Subversion Repository
Password for 'tylersmith': <typed = in password>********
Authentication realm: <http://svn.server.address:80> Subversion Repository
=
Username: <t= yped in username>=C2=A0tylersmith
Password for 'tylersmith':=C2=A0<typed in password>**= ******
'file1.c<= /span>' locked by user '= tylersmith'.
'file2.c' l= ocked by user 't= ylersmith'.
'file3.c'= ; locked by user 'tylersmith'.
<= /div>



<= div>
I set up a test SVN server to support both http:// acces= s as well as svn://. This problem does not occur with svn://. (If this issu= e is a lost cause via http://, I might consider switching if I can get arou= nd the username-password data for svnserve being contained in a plain text = file.)

Looking at a Wireshark trace of the i= nitial command, I get two packets stating "401 Unauthorized". It = is at this point that I am prompted by the command line client for my passw= ord(s). Only after entering all requested information does it send/receive = more packets to/from the SVN server to complete the action.

<= /div>

Is this an issue in the svn client or a but in the= web authentication of the server?


= Thank you for your help,

Tyler Smith
--94eb2c08b3c424f1e4053e334964--