Regarding public/private key pairs, was Re: [laptop.org #7741] project hosting request (resend)

[Henry Hardy]

Regarding public keys required for hosting applications:

The use of public keys is not optional in our security system. Without
a private/public keypair, we could set up a repository but you would
not ever be able to access it.

The ssh key is necessary in order for you to be able to connect to the
repository. It serves in place of a password. If you are not familiar
with the use of public key infrastructure, you can learn about it at
wikipedia:

http://en.wikipedia.org/wiki/Public-key_cryptography

In the Unix/Linux/Mac environment, you can use ssh-keygen to create
the public/private key pair. See
http://www.linuxquestions.org/linux/answers/Networking/Public_key_authentication_with_ssh
for an example. In our case you need only do step one above and
provide us with the public key or a link to it in your application. We
will provision the server with it. You must be responsible to keep
track of your private key as there is no reasonable way to recover it
if lost or compromised.

In the Windows environment, the free program puttygen.exe can be used
to create a public/private key pair, and the program pageant.exe can
be used to facilitate connection to your account using your private
key once we have set up your account with the public key you will
provide to us.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

--HH.
henry at laptop.org

On Tue, Mar 11, 2008 at 7:28 AM,  <Support at rt.laptop.org> wrote:
>
>  Tue Mar 11 07:28:24 2008: Request 7741 was acted upon.
>  Transaction: Ticket created by Victor.Lazzarini at nuim.ie
>        Queue: sysadmin
>      Subject: project hosting request (resend)
>        Owner: Nobody
>   Requestors: Victor.Lazzarini at nuim.ie
>       Status: new
>   Ticket <URL: http://rt.laptop.org/Ticket/Display.html?id=7741 >
>
>
>
>
>
>
>  1. Project name             : csndsugui
>  2. Existing website, if any :
>  3. One-line description     : a toolkit for the development of custom
>  csound activities
>
>  4. Longer description       : csndsugui is a Python-based toolkit for the
>  development of
>                              : activities based on csound under sugar: lab
>  demos, instruments
>                              : and music-related applications. It also aims
>  to provide a simple migration
>                              : path for csound code that uses FLTK widgets.
>
>  5. URLs of similar projects :
>
>  6. Committer list
>     Please list the maintainer (lead developer) as the first entry. Only list
>     developers who need to be given accounts so that they can commit to your
>     project's code repository, or push their own. There is no need to list
>     non-committer developers.
>
>        Username   Full name             SSH2 key URL                    E-mail
>        --------   ---------             ------------                    ------
>     #1           Victor
>  Lazzarini                                      Victor.Lazzarini at nuim.ie
>     #2
>     #3
>        ...
>
>     If any developers don't have their SSH2 keys on the web, please attach
>  them
>     to the application e-mail.
>
>  7. Preferred development model
>
>     [X] Central tree. Every developer can push his changes directly to the
>         project's git tree. This is the standard model that will be
>  familiar to
>         CVS and Subversion users, and that tends to work well for most
>  projects.
>
>     [ ] Maintainer-owned tree. Every developer creates his own git tree, or
>         multiple git trees. He periodically asks the maintainer to look at one
>         or more of these trees, and merge changes into the maintainer-owned,
>         "main" tree. This is the model used by the Linux kernel, and is
>         well-suited to projects wishing to maintain a tighter control on code
>         entering the main tree.
>
>     If you choose the maintainer-owned tree model, but wish to set up some
>     shared trees where all of your project's committers can commit directly,
>     as might be the case with a "discussion" tree, or a tree for an individual
>     feature, you may send us such a request by e-mail, and we will set up the
>     tree for you.
>
>  8. Set up a project mailing list:
>
>     [ ] Yes, named after our project name
>     [ ] Yes, named ______________________
>     [X] No
>
>     When your project is just getting off the ground, we suggest you eschew
>     a separate mailing list and instead keep discussion about your project
>     on the main OLPC development list. This will give you more input and
>     potentially attract more developers to your project; when the volume of
>     messages related to your project reaches some critical mass, we can
>     trivially create a separate mailing list for you.
>
>     If you need multiple lists, let us know. We discourage having many
>     mailing lists for smaller projects, as this tends to
>     stunt the growth of your project community. You can always add more lists
>     later.
>
>  9. Commit notifications
>
>     [ ] Notification of commits to the main tree should be e-mailed to the list
>         we chose to create above
>     [ ] A separate mailing list, <projectname>-git, should be created for
>  commit
>         notifications
>     [X] No commit notifications, please
>
>  10. Shell accounts
>
>     As a general rule, we don't provide shell accounts to developers unless
>     there's a demonstrated need. If you have one, please explain here, and
>     list the usernames of the committers above needing shell access.
>
>  11. Translation
>     [X] Set up the laptop.org Pootle server to allow translation commits to
>  be made
>     [ ] Translation arrangements have already been made at _______________
>
>  12. Notes/comments:
>
>
>
>  I do not have a username or a SSH2 key
>  Victor Lazzarini
>  Music Technology Laboratory
>  Music Department
>  National University of Ireland, Maynooth
>
>
>
>