Following up on what was discussed in the meeting and the list of requirements from the previous email, here are the scripts I'm currently working on to setup the bzr repository.
* scponly-repo.sh: This is the first script to run. It sets up the chroot environment. A portion of this script should be made into a cron job that periodically refreshes the programs and libraries within the chroot (to limit the time that the chroot is vulnerable to exploits.) - A portion of this script needs to be run by root. - This script labels files for SELinux. If SELinux is not enabled on the server this lands on we'll want to comment that out. - A portion of the script sets up a passwd and group file within the chroot. I suspect that this is not necessary.
* setup-repo.sh: This script imports one of the cvs-seed tarballs from cvs.fedora.redhat.com into the new repository. It sets up a sample within the embargo directory as well.
* repo.conf: Apache configuration file to enable access to the repo over http. Note that this allows bzr to access the repository over ssh. It is not a web-front end. There is a separate cgi script which I haven't yet worked with that can be used for that.
* user.sh: Sets up one user with an account on the system; adding them to appropriate groups and etc. This is incomplete until I tie it into the accounts system to retrieve the ssh key. In the future, user information should be created by the accountsdb.
* user-setup.sh: This script sets up default groups (vcsuser and security) that are used by the acls. It also creates a vcsguest account that allows anonymous logins. After implementing http retrieval on my test machine, I don't think this is necessary any longer. Anonymous access can use http to retrieve public information. Read-write access and access to private information will go through sftp.
* sshd_config: Replacement sshd configuration. Changes: - AuthorizedKeysFile is changed to explicitly reference /home/%u instead of the user's home directory. This is so vcusers have their keys extracted from /home/%u instead of their home directory (which is within the chroot). vcsusers do not have access to change ssh keys on the server, this has to be done through the accounts db. - PermitEmptyPasswords, PasswordAuthentication: This is to enable anonymous ssh login to the chroot. Since anonymous access is going to happen over http, this should no longer be necessary. - Subsystem sftp: enabled sftp for bzr.
Everything is a work in progress but my main thrust right now is creating good ACLs and testing what the limitations are.
-Toshio
On 8/4/06, Toshio Kuratomi toshio@tiki-lounge.com wrote:
Following up on what was discussed in the meeting and the list of requirements from the previous email, here are the scripts I'm currently working on to setup the bzr repository.
- scponly-repo.sh: This is the first script to run. It sets up the
chroot environment. A portion of this script should be made into a cron job that periodically refreshes the programs and libraries within the chroot (to limit the time that the chroot is vulnerable to exploits.)
- A portion of this script needs to be run by root.
- This script labels files for SELinux. If SELinux is not enabled on
the server this lands on we'll want to comment that out.
- A portion of the script sets up a passwd and group file within the
chroot. I suspect that this is not necessary.
- setup-repo.sh: This script imports one of the cvs-seed tarballs from
cvs.fedora.redhat.com into the new repository. It sets up a sample within the embargo directory as well.
- repo.conf: Apache configuration file to enable access to the repo over
http. Note that this allows bzr to access the repository over ssh. It is not a web-front end. There is a separate cgi script which I haven't yet worked with that can be used for that.
- user.sh: Sets up one user with an account on the system; adding them
to appropriate groups and etc. This is incomplete until I tie it into the accounts system to retrieve the ssh key. In the future, user information should be created by the accountsdb.
- user-setup.sh: This script sets up default groups (vcsuser and
security) that are used by the acls. It also creates a vcsguest account that allows anonymous logins. After implementing http retrieval on my test machine, I don't think this is necessary any longer. Anonymous access can use http to retrieve public information. Read-write access and access to private information will go through sftp.
- sshd_config: Replacement sshd configuration. Changes:
- AuthorizedKeysFile is changed to explicitly reference /home/%u
instead of the user's home directory. This is so vcusers have their keys extracted from /home/%u instead of their home directory (which is within the chroot). vcsusers do not have access to change ssh keys on the server, this has to be done through the accounts db.
- PermitEmptyPasswords, PasswordAuthentication: This is to enable
anonymous ssh login to the chroot. Since anonymous access is going to happen over http, this should no longer be necessary.
- Subsystem sftp: enabled sftp for bzr.
Everything is a work in progress but my main thrust right now is creating good ACLs and testing what the limitations are.
-Toshio
Hey Toshio, I'm going to have some free time to set this up soon, I seem to remember you mentioning you had updated scripts. If they happen to be ready now send them to the list and I'll get them started.
-Mike
On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote:
Hey Toshio, I'm going to have some free time to set this up soon, I seem to remember you mentioning you had updated scripts. If they happen to be ready now send them to the list and I'll get them started.
Hey Mike,
Tarball here: http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz
or checkout from bzr: bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/
When do you think you'll be starting so I can be around a computer as well?
-Toshio
On 8/11/06, Toshio Kuratomi toshio@tiki-lounge.com wrote:
On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote:
Hey Toshio, I'm going to have some free time to set this up soon, I seem to remember you mentioning you had updated scripts. If they happen to be ready now send them to the list and I'll get them started.
Hey Mike,
Tarball here: http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz
or checkout from bzr: bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/
We've hit a snag. While building bzr for RHEL4 it bombs with a message stating that it requires python 2.4, presently python-2.3.4-14.2 is installed. Suggestions on how to proceed from here?
-Mike
On Friday 11 August 2006 9:50 pm, Mike McGrath wrote:
On 8/11/06, Toshio Kuratomi toshio@tiki-lounge.com wrote:
On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote:
Hey Toshio, I'm going to have some free time to set this up soon, I seem to remember you mentioning you had updated scripts. If they happen to be ready now send them to the list and I'll get them started.
Hey Mike,
Tarball here: http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz
or checkout from bzr: bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/
We've hit a snag. While building bzr for RHEL4 it bombs with a message stating that it requires python 2.4, presently python-2.3.4-14.2 is installed. Suggestions on how to proceed from here?
Backport to python2.3, package python 2.4 in such a way as it is parallel installable with 2.3 ( there is to many things linked to the version of python that is in a distro to upgrade it to 2.4, or use FC5
On Fri, 2006-08-11 at 22:02 -0500, Dennis Gilmore wrote:
On Friday 11 August 2006 9:50 pm, Mike McGrath wrote:
On 8/11/06, Toshio Kuratomi toshio@tiki-lounge.com wrote:
On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote:
Hey Toshio, I'm going to have some free time to set this up soon, I seem to remember you mentioning you had updated scripts. If they happen to be ready now send them to the list and I'll get them started.
Hey Mike,
Tarball here: http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz
or checkout from bzr: bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/
We've hit a snag. While building bzr for RHEL4 it bombs with a message stating that it requires python 2.4, presently python-2.3.4-14.2 is installed. Suggestions on how to proceed from here?
Backport to python2.3, package python 2.4 in such a way as it is parallel installable with 2.3 ( there is to many things linked to the version of python that is in a distro to upgrade it to 2.4, or use FC5
if this is for the primary bzr server let's not use fc5 for it. We need to be able to keep it up for a long-ish time.
-sv
On Friday 11 August 2006 10:29 pm, seth vidal wrote:
On Fri, 2006-08-11 at 22:02 -0500, Dennis Gilmore wrote:
Backport to python2.3, package python 2.4 in such a way as it is parallel installable with 2.3 ( there is to many things linked to the version of python that is in a distro to upgrade it to 2.4, or use FC5
if this is for the primary bzr server let's not use fc5 for it. We need to be able to keep it up for a long-ish time.
thats my inclination also. it will take more work but porting bzr to python 2.3 or making a parallel installable 2.4 would be best options. Just throwing out there what i see as the possible options, I didint say they were good ideas :D
On 8/11/06, seth vidal skvidal@linux.duke.edu wrote:
if this is for the primary bzr server let's not use fc5 for it. We need to be able to keep it up for a long-ish time.
-sv
As of right now its just as a prototype. We've got the SVN server up and running. Long term we could use RHEL5(ish) when it comes out but it would be nice to get this up for the dev's and us to test so see what they think and see what it can do.
-Mike
infrastructure@lists.fedoraproject.org
-
Dennis Gilmore -
Mike McGrath -
seth vidal -
Toshio Kuratomi