dkl is the new release manager for the Bugzilla project and so needs to be able to upload new tarballs to ftp://ftp.mozilla.org/pub/mozilla.org/webtools/. As the assistant project lead, I would also need such privileges to help dkl with releases if necessary. We both already have SSH keys uploaded as we have commit access to bzr.
Summary: Give access to firstname.lastname@example.org and LpSolit@gmail.com to the FTP server to upload new Bugzilla tarballs → Give access to email@example.com and LpSolit@gmail.com to the FTP server to upload new Bugzilla tarballs
I'll vouch for both. LpSolit is our QA manager and probably should have had this for a few years for backup to the release manager anyway. dkl is taking on release duties. Should be set up with local user accounts on surf which match uid/gid with their existing LDAP POSIX accounts (you can get their ssh keys out of the LDAP accounts as well), and be locally placed in the bugzilla group on surf.
Sorry, the group name is webtools, not bugzilla.
Any progress? We are mostly ready with the release stuff.
I've created these users on the 'surf' server with UIDs that match LDAP. I've also added their keys to $HOME/.ssh/authorized_keys, so they should be able to access it. At this point I'm not sure which directory they should be uploading to to distribute the files over FTP however.
(In reply to Ben Kero [:bkero] from comment #4) > At this point I'm not sure which directory they should be uploading to to > distribute the files over FTP however. webtools/ and webtools/archived/
I am still not able to login to stage.mozilla.org which is supposedly where we need to be able to upload bugzilla.org related files. [dkl@localhost bz-release]$ ssh firstname.lastname@example.org Permission denied (publickey). Is the proper key installed? Am I trying the wrong server? wrong id? thanks dkl
Same error message for me.
The problem is now fixed. Thanks!
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
for the record, the user accounts defaulted to locked when created. Had to set the password field to '*' in /etc/shadow to allow them to log in with a key.
(In reply to Frédéric Buclin from comment #8) > The problem is now fixed. Thanks! works for me now too thanks!
You need to log in before you can comment on or make changes to this bug.