RE: password problems - Linux, SVN 1.5.0

Many thanks to Hari Kondugallar.

I commented out the authz-db line in svnserve.conf and I was able to do
a svn import.

Mark Becker

________________________________

From: Hari Kodungallur [mailto:hkodungallur_at_gmail.com]
Sent: Wednesday, June 04, 2008 2:23 PM
To: Mark Becker
Cc: users_at_subversion.tigris.org
Subject: Re: password problems - Linux, SVN 1.5.0

On Wed, Jun 4, 2008 at 10:48 AM, Mark Becker <Mark.Becker_at_nasdaqomx.com>
wrote:

Per Hari Kodungallur requests - contents of conf/svnserve.conf

### This file controls the configuration of the svnserve daemon, if you

### use it to allow access to this repository. (If you only allow

### access through http: and/or file: URLs, then this file is

### irrelevant.)

### Visit http://subversion.tigris.org/ for more information.

[general]

### These options control access to the repository for unauthenticated

### and authenticated users. Valid values are "write", "read",

### and "none". The sample settings below are the defaults.

anon-access = write

auth-access = write

### The password-db option controls the location of the password

### database file. Unless you specify a path starting with a /,

### the file's location is relative to the directory containing

### this configuration file.

### If SASL is enabled (see below), this file will NOT be used.

### Uncomment the line below to use the default password file.

password-db = passwd

### The authz-db option controls the location of the authorization

### rules for path-based access control. Unless you specify a path

### starting with a /, the file's location is relative to the the

### directory containing this file. If you don't specify an

### authz-db, no path-based access control is done.

### Uncomment the line below to use the default authorization file.

authz-db = authz

You have enabled authorization. There is a default authz file in the
conf directory that is pretty much empty (basically, no permission for
anyone).
Did you change this file appropriately to give you permission to write
to the repository?

        ### This option specifies the authentication realm of the
repository.

        ### If two repositories have the same authentication realm, they
should

        ### have the same password database, and vice versa. The
default realm

        ### is repository's uuid.

        realm = PerfEngineering

        [sasl]

        ### This option specifies whether you want to use the Cyrus SASL

        ### library for authentication. Default is false.

        ### This section will be ignored if svnserve is not built with
Cyrus

        ### SASL support; to check, run 'svnserve --version' and look
for a line

        ### reading 'Cyrus SASL authentication is available.'

        # use-sasl = true

        ### These options specify the desired strength of the security
layer

        ### that you want SASL to provide. 0 means no encryption, 1
means

        ### integrity-checking only, values larger than 1 are correlated

        ### to the effective key length for encryption (e.g. 128 means
128-bit

        ### encryption). The values below are the defaults.

        # min-encryption = 0

        # max-encryption = 256

        Mark Becker

        
________________________________

        From: Hari Kodungallur [mailto:hkodungallur_at_gmail.com]
        Sent: Wednesday, June 04, 2008 1:29 PM
        To: Mark Becker
        Cc: users_at_subversion.tigris.org
        Subject: Re: password problems - Linux, SVN 1.5.0

        On Wed, Jun 4, 2008 at 9:23 AM, Mark Becker
<Mark.Becker_at_nasdaqomx.com> wrote:

        I am a SVN newbie and long time unix/linux user and despite
numerous and futile google searches I can't find an answer to why I am
having problems using svn.

        I have edited the conf files and can use svn in file:// mode on
a machine I'll call P3

         conf/passwd contains

        [users]

        becker=becker

        I've tried it with

         becker = becker

        The problem I'm having is after creating a repository, editing
the conf files when I am on P1 and issue

          svn import ctci
svn://p3.corp.com/home/subversion/REPOS/becker - m "initial checkin"

        I see a response <svn://p3.corp.com:3690> MyRealm

        Password for 'becker':

          I respond with becker and get

        Svn: Authorization failed

        If I am on P3 and issue a similar command using file: instead of
svn I don't have a problem.

        I've issued rm -rf ~/.subversion on P1 without effect.

        Suggestions would be greatly appreciated.

        
        Can you show us the contents of the conf/svnserve.conf file?
        The authentication/authorization using conf/svnserve.conf is
used only when you use svn:// protocol. There is no authentication when
you use file://
        
        Regards,
        -Hari

 
Received on 2008-06-04 20:41:13 CEST