On Nov 18, 2008, at 20:36, Ashish Utagikar wrote:
> On Tue, 11/18/08, Ryan Schmidt wrote:
>
>>> I am trying to access my subversion repository
>>> on a California Linux machine from a remote Linux machine in
>>> Arizona using the svn+ssh protocol.
>>>
>>> Unfortunately the repository in California lies inside
>>> a project area. To access it, I need to login to the project
>>> using my user name and password.
>>
>>
>> What is a "project area" and by what means (e.g.
>> http basic authentication, ssh login, etc.) do you need to
>> log in to it?
>>
>>
>>> So when I try to do a commit operation from Arizona it
>>> tries to access the repository and gives me a permission
>>> denied error.
>>>
>>> This is happening because, it cannot automatically log
>>> me in to the project in California with my user name and
>>> password.
>>>
>>> After reading the documentation, I came to know that
>>> for the svn+ssh protocol to work, the svn client needs a
>>> read write access to the repository
>>>
>>> I don’t have this read write access automatically
>>> because it needs me to login to the project.
>>>
>>> I tried writing an expect script for this, which will
>>> automatically login to my project in CA once I am
>>> authenticated by ssh and then I can invoke the svnserve –t
>>> command which can access the repository
>>>
>>> This did not work because it gave me the below error
>>>
>>> svn: Connection closed unexpectedly
>>> error (1)
>>>
>>> We also don’t have any sudo capability
>
>
> Hi Ryan,
> Thanks a lot for your mail. Infact I have seen your name in
> many places when I was searching for answers to my subversion
> questions on the net.
>
> ok when I mean project area, my company has custom script/program
> which they have developed to login to the project and if I want to
> login to the project then I need to give the name of the script
> name followed by the project name
>
> For eg
>
> Linux prompt > <script name> <project name>
>
> This asks for my password and when i enter it I can login to the
> project. This actually forks a complete new sub/new shell where my
> primary group is the project name and it gives me a new linux prompt.
>
> Now I can create files,dirs inside the project etc and work on
> it.So the root dir structure of the project is
>
> /proj/<proj name>
>
> Now I can create files inside /proj/<proj name>
>
> Also every project has around 50 GB of data storage availaible for it.
>
> But if i dont login to the project as above and if i just try to
> access /proj/<proj name> it gives me permission denied error.
>
> So if my subversion repository lies inside the project, say /proj/
> <project name>/subverrepos in CA, then the svn+ssh protocol cannot
> access it from remotely (AZ) because it is unable to login to the
> project using <script name><proj name> automatically on the remote
> machine. So it does not have the read/write access to the /proj/
> <proj name>/subverrepos area, since it could not log me in and it
> fails giving me permission denied error.
>
> I tried writing an expect script which will execute on the remote
> machine and automatically log me in to the project after the ssh
> authentication is completed, but it did not work.
>
> But if i keep the repository outside the project (not in /proj/
> <proj name> area but may be on /tmp of the machine) then i have
> immediate read and write access to the repository and everything
> works great.
>
> Do you have any solution for this problem ?
>
> Is there any way i can keep the repository inside the project or i
> absolutely need to have it outside so that the sshd agent can have
> read/write access to it ?
>
> Thanks again
> Ashish
I don't know how to integrate Subversion with that custom login
script, but I'm replying and sending this back to the Subversion
users list so that maybe someone else can reply. Remember to use
Reply All so your reply goes to the list too, not just to me.
Is there a reason you can't use the existing authentication and
authorization mechanisms that Subversion does provide, which are
documented in the book? http://svnbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-19 05:14:38 CET