GLSA Coordinator Guide分析和总结分析和总结.docxVIP

GLSA Coordinator Guide Content: Prerequisites Accounts A certain number of accounts must be established before working as a GLSA coordinator. To draft GLSAs you must get aGLSAMaker account. To manage security bugs you need to have a Bugzilla account, which will be upgraded to editbugs privileges. To send GLSA announcements you need to have a yourname@ address (i.e. to be a Gentoo developer). This address should be allowed to send to gentoo-announce. To commit XML GLSAs you need your developer account to be upgraded with commit access to the GLSA directory in the gentoo CVS repository. Finally you need an IRC name. You will be required to hang out in the #gentoo-security channel whenever youre available online. Note: Note: All the names used should be consistent in order to allow easy identification. GPG key You must create a GPG key for your yourname@ email address. You can either create a specific key or add the address to an existing key. The key ID should be set in the LDAP, and you should check that your name and key ID appears on the developer list. It is very important that the key is published at least on the keyserver. It can also Environment be submitted on other keyservers. You must setup a CVS environment on your home machine to be able to commit your GLSAs to the tree. This is done by checking out a part of the gentoo CVS repository to a given directory (for example ~/gentoo_cvs): Code Listing 1.1: Setup CVS environment you@home you $ mkdir gentoo_cvs you@home you $ cd gentoo_cvs Code Listing 1.1: Setup CVS environment you@home you $ mkdir gentoo_cvs you@home you $ cd gentoo_cvs you@home gentoo_cvs $ export CVS_RSH=ssh you@home gentoo_cvs $ export CVSROOT=yourname@:/var/cvsroot you@home gentoo_cvs $ cvs checkout gentoo/xml/htdocs/security Mailing-list subscriptions To be able to post to the lists where we publish our GLSAs, you must subscribe your yourname@ address to them: List Subscription page bugtraq@securityfocus.co /archive m Note: You