SVN repository access by password within LAN.

--step 1 -- edit password file
[user@FedoraHome ~]$ vi /var/svn/repos_ebook/conf/passwd

### This file is an example password file for svnserve.
### Its format is similar to that of svnserve.conf. As shown in the
### example below it contains one section labelled [users].
### The name and password for each user follow, one account per line.

[users]
# harry = harrypwd
# sally = sallypwd


--step 2 -- change config file
Has to disable anon-access so that password works on SVN checkout. (on SVN 1.8.8-1 default with Fedora 20)

[user@FedoraHome ~]$vi /var/svn/repos_ebook/conf/svnserve.conf

### The anon-access and auth-access options control access to the
### repository for unauthenticated (a.k.a. anonymous) users and
### authenticated users, respectively.
### Valid values are "write", "read", and "none".
### Setting the value to "none" prohibits both reading and writing;
### "read" allows read-only access, and "write" allows complete
### read/write access to the repository.
### The sample settings below are the defaults and specify that anonymous
### users have read-only access to the repository, while authenticated
### users have read and write access to the repository.
anon-access = none
# auth-access = write

### Uncomment the line below to use the default password file.
password-db = passwd
...........
### Uncomment the line below to use the default authorization file.
# authz-db = authz
### 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 = My ebook Repository


Other advanced access control methods, like via ssh tunnel, apach server. pls refer to SVN user guide Chapter 6 Server Configuration.



ACCESS SVN WITHIN LAN THROUGH TORTOISE SVN CLIENT
--------------------------------------------------