Closed Bug 513087 Opened 15 years ago Closed 15 years ago

Need SVN commit access

Categories

(mozilla.org :: Repository Account Requests, task)

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: richm, Assigned: aravind)

Details

Attachments

(1 file)

      No description provided.
My username is richm@stanfordalumi.org.  I am one of the maintainers of the LDAP C SDK.  I already have CVS and mercurial commit access.  I need to edit the www.mozilla.org/directory content now stored in SVN.  I have tried the svn+ssh method:

svn co svn+ssh://svn.mozilla.org/projects/mozilla.org/trunk/directory/csdk-docs
Permission denied (publickey,gssapi-with-mic).
svn: Connection closed unexpectedly

I've also tried the https method, but I am unable to commit.  It does not like my username (richm@stanfordalumni.org nor richm%stanfordalumni.org) and bugzilla password.
-> mozilla.org.
Assignee: nobody → marcia
Component: www.mozilla.org → Account Request: SVN
Product: Websites → mozilla.org
QA Contact: www-mozilla-org → svn-acct-req
Version: unspecified → other
I guess this can go straight to Server Ops.
Assignee: marcia → server-ops
Assignee: server-ops → phong
** Key appears to be safe. No promises. **
Account created.  Please copy the following into the bug:
=====
Your CVS account has been created.  Your CVSROOT should be:

   richm%stanfordalumi.org@cvs.mozilla.org:/cvsroot

Don't forget to set your CVS_RSH environment variable to 'ssh'.

If you have any problems connecting, let me know.
=====
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Doesn't work:
svn co svn+ssh://svn.mozilla.org/projects/mozilla.org/trunk/directory/csdk-docs
Permission denied (publickey,gssapi-with-mic).
svn: Connection closed unexpectedly

CVSROOT="richm%stanfordalumi.org@cvs.mozilla.org:/cvsroot" svn co svn+ssh://svn.mozilla.org/projects/mozilla.org/trunk/directory/csdk-docs
Permission denied (publickey,gssapi-with-mic).
svn: Connection closed unexpectedly

CVSROOT="richm%stanfordalumi.org@svn.mozilla.org:/cvsroot" svn co svn+ssh://svn.mozilla.org/projects/mozilla.org/trunk/directory/csdk-docs
Permission denied (publickey,gssapi-with-mic).
svn: Connection closed unexpectedly

I was able to checkout using the https method, but when I attempt to commit:
Authentication realm: <https://svn.mozilla.org:443> Mozilla LDAP
Password for 'rich': 
Authentication realm: <https://svn.mozilla.org:443> Mozilla LDAP
Username: richm%stanfordalumni.org@cvs.mozilla.org
Password for 'richm%stanfordalumni.org@cvs.mozilla.org': 
Authentication realm: <https://svn.mozilla.org:443> Mozilla LDAP
Username: richm%stanfordalumni.org@svn.mozilla.org
Password for 'richm%stanfordalumni.org@svn.mozilla.org': 
svn: Commit failed (details follow):
svn: MKACTIVITY of '/!svn/act/8acf11b5-2993-486a-ace8-4e2151ef7177': authorization failed (https://svn.mozilla.org)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #4)
> Your CVS account has been created.  Your CVSROOT should be:
> 
>    richm%stanfordalumi.org@cvs.mozilla.org:/cvsroot

Please delete this CVS account. This bug is about SVN, and the address is richm@stanfordalumni.org, not richm@stanfordalumi.org.
[/projects/mozilla.org/trunk/directory/csdk-docs]
richm@stanfordalumni.org = rw
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Please stop adding random authz things like this. Please remove what you added.

There's clearly a larger issue here, such as bug 509712 just not being done correctly, as evidenced by all these account request bugs.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
still not working for me:

svn co svn+ssh://svn.mozilla.org/projects/mozilla.org/trunk/directory/csdk-docs
Permission denied (publickey,gssapi-with-mic).
svn: Connection closed unexpectedly

One thing - I had to create a new 4096-bit RSA key on August 20, 2008 - it's possible that I did not update mozilla.org with my new pub key - I have attached it to the bug.
already in mozilla-org-trunk group.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
It's still not working - I've tried my old and my new key - both fail
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
aravind: can you debug this for me?
Assignee: phong → aravind
looks like your ssh connections are working.  I have also verified that we have the right public key in ldap.  Here is what I see in the logs.

Aug 31 10:57:33 dm-svn01 sshd[27276]: Accepted publickey for richm@stanfordalumni.org from 76.113.59.19 port 39932 ssh2
Aug 31 10:57:33 dm-svn01 sshd[27276]: pam_unix(sshd:session): session opened for user richm@stanfordalumni.org by (uid=0)

I saw earlier that you tried to use your bugzilla password to commit to the repo.  This will not work.  You should have gotten an e-mail from one of the sysadmins with your LDAP password (that svn uses).  Are you still having problems connecting and committing to the repo?

If you are, please try to find me on irc (aravind) and we can take it from there.
It is working - I just have to specify my login:
svn co svn+ssh://richm@stanfordalumni.org@svn.mozilla.org/projects/mozilla.org/trunk/directory/csdk-docs

It does not like my ~/.ssh/config:
GSSAPIAuthentication yes
GSSAPIDelegateCredentials yes
IdentityFile /home/rich/.ssh/id_rsa-20080820
#LogLevel DEBUG3
Host *.mozilla.org
PreferredAuthentications publickey
User richm@stanfordalumni.org

I cannot figure out how to avoid having to use my userid in the svn+ssh command.  If you guys have any ideas about how to set up my ~/.ssh/config to avoid this, I would appreciate it.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
We usually recommend this.

Host svn.mozilla.org
User richm@stanfordalumni.org


With that in your .ssh/config file, you no longer have to use the username in your checkouts.  Your checkout statement can just say svn co svn+ssh://svn.mozilla.org/blah
Component: Account Request: SVN → Repository Account Requests
QA Contact: svn-acct-req → repo-acct-req
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: