Re: Welcome to gcc.gnu.org

Re: Welcome to gcc.gnu.org

[Dorit Naishlos]

Hi,

The machine from which I sent an SSH key for authentication had crashed;
Do I need to do the same authentication process again from the new machine?

thanks,
dorit



                                                                                                                                     
                      root@sources.redh                                                                                              
                      at.com                   To:       <dnovillo@redhat.com>, dorit@sources.redhat.com, Novillo@sources.redhat.com 
                                               cc:       Diego@sources.redhat.com                                                    
                      15/09/2003 16:45         Subject:  Welcome to gcc.gnu.org                                                      
                                                                                                                                     




Your account is now active, the login name is dorit@gcc.gnu.org.  Mail
sent to that address is forwarded to dorit@il.ibm.com.  This forwarding
is a convenience so that people who reply directly to CVS commit mail
notes will not get a bounce--publicize it at your own risk.  If your
involvement with the project ends at some point, the mail address will
become invalid and I will laugh evilly as people try in vain to reach you.

You have been assigned edit rights to the gcc Bugzilla bug reporting
database.  Your password is doritpass.

You should now have write access to the gcc repository with
SSH+cvs.  Here are lots of details about how to do things.

You don't have general shell access, just CVS remote access.  Just about
everything can be done via CVS.  If there is some special requirement
that you have where you need shell access, talk to your project's lead
and have them talk to overseers@gcc.gnu.org.  In special cases,
we can be flexible on this requirement.

Regarding SSH: If you have provided a Protocol 1 ssh key, you will need
to add the following lines to your a .ssh/config directory:

    Host gcc.gnu.org
             Protocol 1

This will cause your ssh connections to properly default to protocol 1
when connecting to gcc.gnu.org.  If you have provided "Protocol 2"
rsa/dsa keys, then no special action is required.


CVS  CVS is used for revision control.  If you are not familiar with CVS,
     you have some reading to do.  http://cvshome.org/ is the central
     source for all things CVS.  http://cvshome.org/docs/ has some
     useful information.

     When you want to do a check-in of some change, do it like this:

     % cvs update
     % cvs diff      # carefully verify what you're about to check in!
     % cvs commit

     All of the sources are under CVS.  You have write access to the
     files in your repository.  Check them out like this:

     export CVS_RSH=ssh
     cvs -z9 -d :ext:dorit@gcc.gnu.org:/cvs/gcc co gcc

     After you've checked out some files, you won't need to specify the
     CVSROOT (-d) again, it will be picked out of the CVS control files
     (the CVS/Root file).  You will need to include the -z9; you can put
     it in your $HOME/.cvsrc file ("cvs -z9") or add it to your command
     line whenever you're doing CVS operations.

     If you're going over a modem, you'll definitely want to get this
     as compressed as possible.

     To avoid the nuisance of having to supply your passphrase for each
     operation, you may want to use ssh-agent(1) followed by ssh-add(1)
     and entering your passphrase once for all.  Either start your
     session as a child of ssh-agent or run it as a demon and set the
     values of the environment variables SSH_AUTHENTICATION_SOCKET and
     SSH_AGENT_PID in each relevant process to what ssh-agent prints
     when it starts.  To avoid messages about (lack of) X11 forwarding,
     put in your $HOME/.ssh/config and entry like:

        Host gcc.gnu.org
        ForwardX11 no

CVS COMMIT MESSAGES
     You can get e-mail notifications for when things are checked in to
     your group's repository.  There are two notification mailing lists,
     one for the web pages for your project and one for the project
     source files.  To subscribe to your source-file-notification list,
     send a message to

         gcc-cvs-subscribe@gcc.gnu.org

     To get on a digest of the above list (get one note a day), send a
     note to

         gcc-cvs-digest-subscribe@gcc.gnu.org

     The body/Subject are ignored in these messages.  The From: address
     is the one you a requesting to subscribe.  To request an arbitrary
     address be subscribed, say foo@bar.com, send a note like this:

         gcc-cvs-subscribe-foo=bar.com@gcc.gnu.org

     If your project has a web page, then there is a second mailing
     list for notifications about changes to them.  The addresses are
     just like the above ones except they include "-webpages" after the
     project name.  For instance,

         gcc-webpages-cvs-digest-subscribe@gcc.gnu.org


     If this is all a little confusing, just use the all-doing
     auto-subscriber at
        http://gcc.gnu.org/ml/lists.html#faqs

CVSWEB You can browse changes that are being made to the CVS repository by
     going to

             http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc?cvsroot=gcc

HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
     also under CVS.  You can create a home page (if one doesn't already
     exist) for gcc by putting files in the htdocs/ directory of
     your CVS repository.  They will appear instantly (within three or
     four seconds, anyway) at http://gcc.gnu.org/gcc/

If anything is unanswered, please ask your project mailing list.

Re: Welcome to gcc.gnu.org

[Gerald Pfeifer]

On Wed, 1 Oct 2003, Dorit Naishlos wrote:
> The machine from which I sent an SSH key for authentication had crashed;

I cannot answer this, but why did you send the SSH key of a machine
instead of using a _personal_ SSH key (which you can copy to arbitrarily
many hosts)?

Please refer to `man ssh-keygen` for details.

Gerald
-- 
Gerald Pfeifer (Jerry)   gerald@pfeifer.com   http://www.pfeifer.com/gerald/

Re: Welcome to gcc.gnu.org

[Joseph S. Myers]

A few bits in this standard message need tweaking further for GCC ...:

>      If your project has a web page, then there is a second mailing
>      list for notifications about changes to them.  The addresses are
>      just like the above ones except they include "-webpages" after the
>      project name.  For instance,
> 
>          gcc-webpages-cvs-digest-subscribe@gcc.gnu.org

Or, rather, gcc-cvs-wwwdocs.

>      If this is all a little confusing, just use the all-doing
>      auto-subscriber at
>         http://gcc.gnu.org/ml/lists.html#faqs

No /ml or #faqs in the correct URL.

> HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
>      also under CVS.  You can create a home page (if one doesn't already
>      exist) for gcc by putting files in the htdocs/ directory of
>      your CVS repository.  They will appear instantly (within three or
>      four seconds, anyway) at http://gcc.gnu.org/gcc/

No /gcc/.

-- 
Joseph S. Myers
jsm@polyomino.org.uk

Re: Welcome to gcc.gnu.org

[Dorit Naishlos]

> why did you send the SSH key of a machine
> instead of using a _personal_ SSH key (which you can copy to arbitrarily
> many hosts)?
>
I did create a personal key, but unfortunately I don't have access to the
files that contain the private and public keys that I had generated
(they are in the corrupted disk from which I cannot recover data anymore).
So, I need to generate new keys, and the question is -
how do I send my new public key - do I need to fill up the same on-line
form? the form says:
                                                                            
 "Note that if you already have an account on sources.redhat.com or         
 gcc.gnu.org for CVS write access, then do not use this form. Instead send  
 an email to the overseers mail account..."                                 
                                                                            
 thanks,                                                                    
 dorit                                                                      
                                                                            
                                                                            





                                                                                                                                     
                      Gerald Pfeifer                                                                                                 
                      <gerald@pfeifer.c        To:       Dorit Naishlos/Haifa/IBM@IBMIL                                              
                      om>                      cc:       overseers@gcc.gnu.org                                                       
                                               Subject:  Re: Welcome to gcc.gnu.org                                                  
                      01/10/2003 12:54                                                                                               
                                                                                                                                     




On Wed, 1 Oct 2003, Dorit Naishlos wrote:
> The machine from which I sent an SSH key for authentication had crashed;

I cannot answer this, but why did you send the SSH key of a machine
instead of using a _personal_ SSH key (which you can copy to arbitrarily
many hosts)?

Please refer to `man ssh-keygen` for details.

Gerald
--
Gerald Pfeifer (Jerry)   gerald@pfeifer.com
http://www.pfeifer.com/gerald/

Re: Welcome to gcc.gnu.org

[Christopher Faylor]

On Wed, Oct 01, 2003 at 12:22:15PM +0100, Joseph S. Myers wrote:
>A few bits in this standard message need tweaking further for GCC ...:
>
>>      If your project has a web page, then there is a second mailing
>>      list for notifications about changes to them.  The addresses are
>>      just like the above ones except they include "-webpages" after the
>>      project name.  For instance,
>> 
>>          gcc-webpages-cvs-digest-subscribe@gcc.gnu.org
>
>Or, rather, gcc-cvs-wwwdocs.
>
>>      If this is all a little confusing, just use the all-doing
>>      auto-subscriber at
>>         http://gcc.gnu.org/ml/lists.html#faqs
>
>No /ml or #faqs in the correct URL.
>
>> HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
>>      also under CVS.  You can create a home page (if one doesn't already
>>      exist) for gcc by putting files in the htdocs/ directory of
>>      your CVS repository.  They will appear instantly (within three or
>>      four seconds, anyway) at http://gcc.gnu.org/gcc/
>
>No /gcc/.

Here's the script.  Patch it as you see fit and send the diff here.
Remember that it handles gcc and sources.redhat.com requests.

cgf
#! /bin/sh

# Usage: create-user USERNAME FULL-NAME GROUP-NAME FORWARD-ADDR SSH-FILE
# USERNAME - login id
# FULL-NAME - a single argument which is the user's first+last names
# GROUP-NAME - Primary group for user.  This is the group of the project
#              he's being given access to.
# FORWARD-ADDR - forwarding email address
# SSH-FILE - File containing ssh key.  VALIDATE THIS BY HAND!
# MODULE - name of module they should check out

if test "$#" -lt 6 -o "$#" -gt 7; then
   echo "usage: create-user USERNAME FULL-NAME GROUP-NAME FORWARD-ADDR SSH-FILE MODULE [APPROVER]" 1>&2
   exit 1
fi

username="$1"
fullname="$2"
groupname="$3"
forward="$4"
sshfile="$5"
module="$6"
approved="$7"

KNOWN_UID=0
case "$username" in
    *-*)
	IFS='-'
	set $username
	username=$1 KNOWN_UID=$2
	IFS=' 	'
	export KNOWN_UID
esac

uhome=/home/$username

if test x"$sshfile" != 'x-'; then
    if test "`wc -l < $sshfile`" -ne 1; then
       echo "create-user: more than one line in \`$sshfile'" 1>&2
       exit 1
    fi
fi

# Don't redirect grep -- let user see the output.
# Ignore differences in case when looking for username clash.
if grep -i "^${username}:" /etc/passwd; then
   echo "create-user: user \`$username' already exists" 1>&2
   exit 1
fi

grep -i "^${groupname}:" /etc/group > /dev/null 2>&1 || {
   echo "create-user: group \`$groupname' does not exist" 1>&2
   exit 1
}

# First, create the new user.  This is tricky: we set EDITOR to be a
# shell script which does the actual dirty work for us and then use
# vipw to invoke it.
(EDITOR=create-user-helper
export EDITOR
USERNAME="$username"
export USERNAME
GROUPNAME="$groupname"
export GROUPNAME
FULLNAME="$fullname"
export FULLNAME
# FIXME: ok, we'd like to use `vipw' here, but it doesn't seem to work.
# Bummer.
# vipw
$EDITOR /etc/passwd
) || {
   echo "create-user: couldn't edit password file" 1>&2
   exit 1
}

# If the user is in a src-related group, add him to the src group if
# he isn't already in it.
case "$groupname" in
 cygwin | dejagnu | binutils | gdb | insight | cgen | sid)
    # This is much nicer than the portable method.
    usermod -G src $username
    cvsgroup=src
    ;;

 *)
    cvsgroup=$groupname
    ;;
esac

# Create the user's home.
test -d $uhome || mkdir $uhome || {
   echo "create-user: couldn't create \`$uhome'" 1>&2
   exit 1
}

# Email forwarding.
(echo "$forward" > $uhome/.qmail) || {
   echo "create-user: couldn't create \`$uhome/.qmail'" 1>&2
   exit 1
}

# Login ability.
test -d $uhome/.ssh || mkdir $uhome/.ssh || {
   echo "create-user: couldn't create \`$uhome/.ssh'" 1>&2
   exit 1
}

(echo -n 'no-port-forwarding,no-X11-forwarding,no-agent-forwarding,command="/usr/local/bin/cvs server" ' > $uhome/.ssh/authorized_keys \
   && cat "$sshfile" >> $uhome/.ssh/authorized_keys
) || {
   echo "create-user: couldn't create \`$uhome/.ssh/authorized_keys'" 1>&2
   exit 1
}

ok=no
chown -R $username.$groupname $uhome \
   && chmod 2755 $uhome $uhome/.ssh \
   && chmod 644 $uhome/.qmail $uhome/.ssh/authorized_keys \
   && ok=yes

if test "$ok" = no; then
   echo "create-user: couldn't set permissions on user files" 1>&2
   exit 1
fi

gnatspass=''
case "$groupname" in
    *gcc*|*java*|*c++*)
	sys=gcc.gnu.org
	gnatspass="$username"pass
	echo "adding $username to bugzilla"
	bugzilla-createuser $username "$gnatspass"
	gnatspass="password is $gnatspass"
	bugger=Bugzilla
	;;
    *)
	sys=sources.redhat.com
	gnatsdir=/sourceware/gnats/${groupname}-db
	if test -d $gnatsdir; then
	    echo "adding $username to gnats"
	    gnatspass="`gnatsadd $username $groupname $sys`"
	    case "$gnatspass" in
		password\ is\ *) ;;
		*)		gnatspass='' ;;
	    esac
	fi
	bugger=GNATS
	;;
esac

fmt > /tmp/welcome-$username << END
Your account is now active, the login name is
$username@$sys.  Mail sent to that address is forwarded
to $forward.  This forwarding is a convenience so that people who reply
directly to CVS commit mail notes will not get a bounce--publicize it at
your own risk.  If your involvement with the project ends at some point,
the mail address will become invalid and I will laugh evilly as people
try in vain to reach you.
END

[ -n "$gnatspass" ] && cat >> /tmp/welcome-$username << END

You have been assigned edit rights to the $groupname $bugger bug reporting
database.  Your $gnatspass.
END

cat >> /tmp/welcome-$username << END

You should now have write access to the $cvsgroup repository with
SSH+cvs.  Here are lots of details about how to do things.

You don't have general shell access, just CVS remote access.  Just about
everything can be done via CVS.  If there is some special requirement
that you have where you need shell access, talk to your project's lead
and have them talk to overseers@$sys.  In special cases,
we can be flexible on this requirement.

Regarding SSH: If you have provided a Protocol 1 ssh key, you will need
to add the following lines to your a .ssh/config directory:

    Host $sys
	Protocol 1

This will cause your ssh connections to properly default to protocol 1
when connecting to $sys.  If you have provided "Protocol 2"
rsa/dsa keys, then no special action is required.


CVS  CVS is used for revision control.  If you are not familiar with CVS,
     you have some reading to do.  http://cvshome.org/ is the central
     source for all things CVS.  http://cvshome.org/docs/ has some
     useful information.

     When you want to do a check-in of some change, do it like this:

     % cvs update
     % cvs diff      # carefully verify what you're about to check in!
     % cvs commit

     All of the sources are under CVS.  You have write access to the
     files in your repository.  Check them out like this:

     export CVS_RSH=ssh
     cvs -z9 -d :ext:$username@$sys:/cvs/$cvsgroup co $module

     After you've checked out some files, you won't need to specify the
     CVSROOT (-d) again, it will be picked out of the CVS control files
     (the CVS/Root file).  You will need to include the -z9; you can put
     it in your \$HOME/.cvsrc file ("cvs -z9") or add it to your command
     line whenever you're doing CVS operations.

     If you're going over a modem, you'll definitely want to get this
     as compressed as possible.

     To avoid the nuisance of having to supply your passphrase for each
     operation, you may want to use ssh-agent(1) followed by ssh-add(1)
     and entering your passphrase once for all.  Either start your
     session as a child of ssh-agent or run it as a demon and set the
     values of the environment variables SSH_AUTHENTICATION_SOCKET and
     SSH_AGENT_PID in each relevant process to what ssh-agent prints
     when it starts.  To avoid messages about (lack of) X11 forwarding,
     put in your \$HOME/.ssh/config and entry like:

        Host $sys
        ForwardX11 no 

CVS COMMIT MESSAGES
     You can get e-mail notifications for when things are checked in to
     your group's repository.  There are two notification mailing lists,
     one for the web pages for your project and one for the project
     source files.  To subscribe to your source-file-notification list,
     send a message to

         $groupname-cvs-subscribe@$sys

     To get on a digest of the above list (get one note a day), send a 
     note to 

         $groupname-cvs-digest-subscribe@$sys

     The body/Subject are ignored in these messages.  The From: address
     is the one you a requesting to subscribe.  To request an arbitrary
     address be subscribed, say foo@bar.com, send a note like this:

         $groupname-cvs-subscribe-foo=bar.com@$sys

     If your project has a web page, then there is a second mailing
     list for notifications about changes to them.  The addresses are
     just like the above ones except they include "-webpages" after the
     project name.  For instance,

         $groupname-webpages-cvs-digest-subscribe@$sys


     If this is all a little confusing, just use the all-doing 
     auto-subscriber at
        http://$sys/ml/lists.html#faqs

CVSWEB You can browse changes that are being made to the CVS repository by
     going to

	http://$sys/cgi-bin/cvsweb.cgi/$module?cvsroot=$cvsgroup

HTTP All of the web pages on http://$sys/$groupname/ are
     also under CVS.  You can create a home page (if one doesn't already
     exist) for $groupname by putting files in the htdocs/ directory of
     your CVS repository.  They will appear instantly (within three or
     four seconds, anyway) at http://$sys/$groupname/

If anything is unanswered, please ask your project mailing list.
END

echo -n "Hit enter to inspect /tmp/welcome-$username..."; read a < /dev/tty
less -c /tmp/welcome-$username
if [ -n "$approved" ]; then
    mail="mail -c $approved"
else
    mail='mail'
fi

echo -n "Hit enter to send $mail $username otherwise hit CTRL-C..."; read a < /dev/tty
$mail -s "Welcome to $sys" $username < /tmp/welcome-$username
echo "Done."

exit 0

Re: Welcome to gcc.gnu.org

[Gerald Pfeifer]

On Wed, 1 Oct 2003, Christopher Faylor wrote:
> On Wed, Oct 01, 2003 at 12:22:15PM +0100, Joseph S. Myers wrote:
>> A few bits in this standard message need tweaking further for GCC ...:

Yup.

>>> HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
>>>      also under CVS.  You can create a home page (if one doesn't already
>>>      exist) for gcc by putting files in the htdocs/ directory of
>>>      your CVS repository.  They will appear instantly (within three or
>>>      four seconds, anyway) at http://gcc.gnu.org/gcc/
>>
>> No /gcc/.

And in fact also the note on the CVS repository needs an update (it should
read module, and for GCC web pages are in a module of their own).

> Here's the script.  Patch it as you see fit and send the diff here.
> Remember that it handles gcc and sources.redhat.com requests.

How about the following?  I tried to address all issues quoted above,
but couldn't test this properly.

Hope this helps,
Gerald

--- s.orig	Thu Oct  2 23:38:14 2003
+++ s	Thu Oct  2 23:37:58 2003
@@ -127,6 +127,8 @@ gnatspass=''
 case "$groupname" in
     *gcc*|*java*|*c++*)
 	sys=gcc.gnu.org
+	website=http://$sys
+	webcvsmodule=wwwdocs
 	gnatspass="$username"pass
 	echo "adding $username to bugzilla"
 	bugzilla-createuser $username "$gnatspass"
@@ -135,6 +137,8 @@ case "$groupname" in
 	;;
     *)
 	sys=sources.redhat.com
+	website=http://$sys/$groupname/
+	webcvsmodule=$groupname
 	gnatsdir=/sourceware/gnats/${groupname}-db
 	if test -d $gnatsdir; then
 	    echo "adding $username to gnats"
@@ -261,11 +265,11 @@ CVSWEB You can browse changes that are b

 	http://$sys/cgi-bin/cvsweb.cgi/$module?cvsroot=$cvsgroup

-HTTP All of the web pages on http://$sys/$groupname/ are
+HTTP All of the web pages on $website are
      also under CVS.  You can create a home page (if one doesn't already
      exist) for $groupname by putting files in the htdocs/ directory of
-     your CVS repository.  They will appear instantly (within three or
-     four seconds, anyway) at http://$sys/$groupname/
+     the $webcvsmodule CVS module.  They will appear instantly (within three
+     or four seconds, anyway) at $website

 If anything is unanswered, please ask your project mailing list.
 END

Re: Welcome to gcc.gnu.org

[Christopher Faylor]

On Thu, Oct 02, 2003 at 11:43:24PM +0200, Gerald Pfeifer wrote:
>On Wed, 1 Oct 2003, Christopher Faylor wrote:
>> On Wed, Oct 01, 2003 at 12:22:15PM +0100, Joseph S. Myers wrote:
>>> A few bits in this standard message need tweaking further for GCC ...:
>
>Yup.
>
>>>> HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
>>>>      also under CVS.  You can create a home page (if one doesn't already
>>>>      exist) for gcc by putting files in the htdocs/ directory of
>>>>      your CVS repository.  They will appear instantly (within three or
>>>>      four seconds, anyway) at http://gcc.gnu.org/gcc/
>>>
>>> No /gcc/.
>
>And in fact also the note on the CVS repository needs an update (it should
>read module, and for GCC web pages are in a module of their own).
>
>> Here's the script.  Patch it as you see fit and send the diff here.
>> Remember that it handles gcc and sources.redhat.com requests.
>
>How about the following?  I tried to address all issues quoted above,
>but couldn't test this properly.

Looks good.  I checked it in.  I also added a fix for the reference to
web cvs  subscriptions, too.  You should see the result here soon, so
please inspect it for accuracy.

Thanks, Gerald

cgf

Re: Welcome to gcc.gnu.org

[Joel Sherrill]

On December 17, 2014 11:50:34 PM PST, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote:
>Hello,
>
>I need also write permission for Newlib and Binutils.

They are on the same server and technically you do have permission but my experience is to treat it as write after approval.

>On 17/12/14 16:29, root@sourceware.org wrote:
>> Your account is now active, the login name is sh@gcc.gnu.org.  Mail
>sent
>> to that address is forwarded to sebastian.huber@embedded-brains.de.
>> This forwarding is a convenience so that people who reply directly to
>> source control commit mail notes will not get a bounce.  This is not
>> intended as a general mail account.  Please do not advertise it.
>>
>> If your involvement with the project ends at some point, the mail
>address
>> will become invalid and I will laugh evilly as people try in vain to
>> reach you.  We do track these things.
>>
>> You should now have write access to the source control repository for
>> your project.  Presumably you know where things are and how to access
>> them.  If not, check with your project web page and with the person
>who
>> sponsored you.
>>
>> You have restricted (not login!) ssh access to the system so if at
>some
>> point you wish to update your ssh key, you can do so with the
>following
>> command:
>>
>>      ssh gcc.gnu.org appendkey < publickeyfile
>>
>> This will append 'publickeyfile' (usually ~/.ssh/id_dsa.pub or
>> ~/.ssh/id_rsa.pub) to your existing allowed ssh keys. If you have
>entirely
>> lost your old ssh key, then grovel to overseers@gcc.gnu.org and
>someone
>> may take pity on you. If you suspect your key has been compromised,
>> let the overseers know as soon as possible.
>>
>> You can also update your email forwarding with the command:
>>
>>      ssh gcc.gnu.org email your@newmail.com
>>
>> If you have questions, please do not reply to this email.  Ask your
>> project mailing list.

--joel

Re: Welcome to gcc.gnu.org

[Sebastian Huber]

Hello,

I need also write permission for Newlib and Binutils.

On 17/12/14 16:29, root@sourceware.org wrote:
> Your account is now active, the login name is sh@gcc.gnu.org.  Mail sent
> to that address is forwarded to sebastian.huber@embedded-brains.de.
> This forwarding is a convenience so that people who reply directly to
> source control commit mail notes will not get a bounce.  This is not
> intended as a general mail account.  Please do not advertise it.
>
> If your involvement with the project ends at some point, the mail address
> will become invalid and I will laugh evilly as people try in vain to
> reach you.  We do track these things.
>
> You should now have write access to the source control repository for
> your project.  Presumably you know where things are and how to access
> them.  If not, check with your project web page and with the person who
> sponsored you.
>
> You have restricted (not login!) ssh access to the system so if at some
> point you wish to update your ssh key, you can do so with the following
> command:
>
>      ssh gcc.gnu.org appendkey < publickeyfile
>
> This will append 'publickeyfile' (usually ~/.ssh/id_dsa.pub or
> ~/.ssh/id_rsa.pub) to your existing allowed ssh keys. If you have entirely
> lost your old ssh key, then grovel to overseers@gcc.gnu.org and someone
> may take pity on you. If you suspect your key has been compromised,
> let the overseers know as soon as possible.
>
> You can also update your email forwarding with the command:
>
>      ssh gcc.gnu.org email your@newmail.com
>
> If you have questions, please do not reply to this email.  Ask your
> project mailing list.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

RE: Welcome to gcc.gnu.org

[Paulo Matos]

Hello,

After creating my email pmatos@gcc.gnu.org you created as well a bugzilla acct. However I had one already.
Can you please delete the pmatos@gcc.gnu.org so I can add my gcc email address to my existing account (currently under paulo@matos-sorge.com)?

Thanks,

Paulo Matos


> -----Original Message-----
> From: zroot@sourceware.org [mailto:zroot@sourceware.org]
> Sent: 24 September 2013 15:47
> To: pmatos@sourceware.org
> Cc: richard.guenther@gmail.com
> Subject: Welcome to gcc.gnu.org
> 
> Your account is now active, the login name is pmatos@gcc.gnu.org.
> Mail sent to that address is forwarded to pmatos@broadcom.com.
> This forwarding is a convenience so that people who reply directly to
> source control commit mail notes will not get a bounce.  This is not
> intended as a general mail account.  Please do not advertise it.
> 
> If your involvement with the project ends at some point, the mail address
> will become invalid and I will laugh evilly as people try in vain to
> reach you.  We do track these things.
> 
> You should now have write access to the source control repository for
> your project.  Presumably you know where things are and how to access
> them.  If not, check with your project web page and with the person who
> sponsored you.
> 
> You have restricted (not login!) ssh access to the system so if at some
> point you wish to update your ssh key, you can do so with the following
> command:
> 
>     ssh gcc.gnu.org appendkey < publickeyfile
> 
> This will append 'publickeyfile' (usually ~/.ssh/id_dsa.pub or
> ~/.ssh/id_rsa.pub) to your existing allowed ssh keys. If you have entirely
> lost your old ssh key, then grovel to overseers@gcc.gnu.org and someone
> may take pity on you. If you suspect your key has been compromised,
> let the overseers know as soon as possible.
> 
> You can also update your email forwarding with the command:
> 
>     ssh gcc.gnu.org email your@newmail.com
> 
> If you have questions, please do not reply to this email.  Ask your
> project mailing list.

Re: Welcome to gcc.gnu.org

[Ian Lance Taylor]

Daniel Towner <daniel.towner@picochip.com> writes:

> I was given cvs-write access to the gcc CVS repository about 2 years
> ago. As it turns out, I never needed this access, and I haven't  logged
> into the account since. That has now changed as I will be submitting a
> new gcc port in the next week or so. The machine that I originally
> configured for write access to the CVS repository is no more, and
> consequently I no longer have the ssh key that I originally used in the
> account setup. Can I change the ssh key to a new value?

Done.

Ian

Re: Welcome to gcc.gnu.org

[Daniel Towner]

Hi,

I was given cvs-write access to the gcc CVS repository about 2 years
ago. As it turns out, I never needed this access, and I haven't  logged
into the account since. That has now changed as I will be submitting a
new gcc port in the next week or so. The machine that I originally
configured for write access to the CVS repository is no more, and
consequently I no longer have the ssh key that I originally used in the
account setup. Can I change the ssh key to a new value?

Thanks,

dan.

----------------------------
New contents of .ssh/id_rsa.pub

ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAIEAzf+QKH88zSCV+4sm/yyS6JEmv/50Wz30PPO3fULD248Drsq3rIVjlU3vnfqB0Iaa6syf9YXxIIRtfjMLw763lrLv5ghkRGIDWDRgSBqTRlfhIdKuKDxZoYRN61OAWydy6dmQCx+qcReXFcKySa4wbOWbcVdHsLsGYXyinewidF0= 

dant@frome.picochip.com


-----------------------------

root@sources.redhat.com wrote:

>  Your account is now active, the login name is dwtowner@gcc.gnu.org.
>  Mail sent to that address is forwarded to dant@picochip.com. This
>  forwarding is a convenience so that people who reply directly to CVS
>  commit mail notes will not get a bounce--publicize it at your own
>  risk. If your involvement with the project ends at some point, the
>  mail address will become invalid and I will laugh evilly as people
>  try in vain to reach you.
>
>  You have been assigned edit rights to the gcc GNATS bug reporting
>  database. Your password is "dwtownerpass".
>
>  You should now have write access to the gcc repository with SSH+cvs.
>  Here are lots of details about how to do things.
>
>  You don't have general shell access, just CVS remote access. Just
>  about everything can be done via CVS. If there is some special
>  requirement that you have where you need shell access, talk to your
>  project's lead and have them talk to overseers@gcc.gnu.org. In
>  special cases, we can be flexible on this requirement.
>
>  Regarding SSH: If you have provided a Protocol 1 ssh key, you will
>  need to add the following lines to your a .ssh/config directory:
>
>  Host gcc.gnu.org Protocol 1
>
>  This will cause your ssh connections to properly default to protocol
>  1 when connecting to gcc.gnu.org. If you have provided "Protocol 2"
>  rsa/dsa keys, then no special action is required.
>
>
>  CVS CVS is used for revision control. If you are not familiar with
>  CVS, you have some reading to do. http://cvshome.org/ is the central
>  source for all things CVS. http://cvshome.org/docs/ has some useful
>  information.
>
>  When you want to do a check-in of some change, do it like this:
>
>  % cvs update % cvs diff # carefully verify what you're about to
>  check in! % cvs commit
>
>  All of the sources are under CVS. You have write access to the files
>  in your repository. Check them out like this:
>
>  export CVS_RSH=ssh cvs -z9 -d :ext:dwtowner@gcc.gnu.org:/cvs/gcc co
>  gcc
>
>  After you've checked out some files, you won't need to specify the
>  CVSROOT (-d) again, it will be picked out of the CVS control files
>  (the CVS/Root file). You will need to include the -z9; you can put
>  it in your $HOME/.cvsrc file ("cvs -z9") or add it to your command
>  line whenever you're doing CVS operations.
>
>  If you're going over a modem, you'll definitely want to get this as
>  compressed as possible.
>
>  To avoid the nuisance of having to supply your passphrase for each
>  operation, you may want to use ssh-agent(1) followed by ssh-add(1)
>  and entering your passphrase once for all. Either start your session
>  as a child of ssh-agent or run it as a demon and set the values of
>  the environment variables SSH_AUTHENTICATION_SOCKET and SSH_AGENT_PID
>  in each relevant process to what ssh-agent prints when it starts. To
>  avoid messages about (lack of) X11 forwarding, put in your
>  $HOME/.ssh/config and entry like:
>
>  Host gcc.gnu.org ForwardX11 no
>
>  CVS COMMIT MESSAGES You can get e-mail notifications for when things
>  are checked in to your group's repository. There are two
>  notification mailing lists, one for the web pages for your project
>  and one for the project source files. To subscribe to your
>  source-file-notification list, send a message to
>
>  gcc-cvs-subscribe@gcc.gnu.org
>
>  To get on a digest of the above list (get one note a day), send a
>  note to
>
>  gcc-cvs-digest-subscribe@gcc.gnu.org
>
>  The body/Subject are ignored in these messages. The From: address is
>  the one you a requesting to subscribe. To request an arbitrary
>  address be subscribed, say foo@bar.com, send a note like this:
>
>  gcc-cvs-subscribe-foo=bar.com@gcc.gnu.org
>
>  If your project has a web page, then there is a second mailing list
>  for notifications about changes to them. The addresses are just like
>  the above ones except they include "-webpages" after the project
>  name. For instance,
>
>  gcc-webpages-cvs-digest-subscribe@gcc.gnu.org
>
>
>  If this is all a little confusing, just use the all-doing
>  auto-subscriber at http://gcc.gnu.org/ml/lists.html#faqs
>
>  CVSWEB You can browse changes that are being made to the CVS
>  repository by going to
>
>  http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc?cvsroot=gcc
>
>  HTTP All of the web pages on http://gcc.gnu.org/gcc/ are also under
>  CVS. You can create a home page (if one doesn't already exist) for
>  gcc by putting files in the htdocs/ directory of your CVS repository.
>  They will appear instantly (within three or four seconds, anyway) at
>  http://gcc.gnu.org/gcc/
>
>  If anything is unanswered, please ask your project mailing list.


-- 
============================================================================
Dr Daniel Towner
picoChip Designs Ltd, Riverside Buildings, 108, Walcot Street, BATH, BA1 5BG
daniel.towner@picochip.com
+44 (0) 7786 702589

Re: Welcome to gcc.gnu.org

[Steven Bosscher]

Yippee, I got my CVS read/write account today, thank you.

But...  Some comments on the confirmation mail I received:


On Sat 22 Feb 2003  20:22, root@sources.redhat.com wrote:
--- 8< ---
> HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
						^^^^^^^
That's a 404.  Should be just "http://gcc.gnu.org/" I suppose?


>      also under CVS.  You can create a home page (if one doesn\'t already
								^^^^
Overzealously escaped.


>      exist) for gcc by putting files in the htdocs/ directory of
>      your CVS repository.  They will appear instantly (within three or
>      four seconds, anyway) at http://gcc.gnu.org/gcc/
						^^^^^^^^

Another one.

> If anything is unanswered, please ask your project mailing list.

The rest of that message seems to be OK.

Greetz
Steven

Re: Welcome to gcc.gnu.org

[Benjamin Kosnik]

>> > will become invalid and I will laugh evilly as people try in vain to
>> > reach you.
>> 
>> Perhaps we ought to remove the part about laughin evilly?  Not all (new)
>> contributors might grok this kind of humor...
>
>I know it's very English-centric, but I think it's imperative we
>keep this.  There's so little humor on the site as it is.  Anyone
>who can push a patch past the oft-obstinate gcc and gdb patch
>approval processes MUST have a sense of humor to make it this far. :-)

Absolutely agreed, seconded.

-benjamin

Re: Welcome to gcc.gnu.org

[Christopher Faylor]

On Wed, Jan 22, 2003 at 03:28:06PM -0800, Jason Molenda wrote:
>On Wed, Jan 22, 2003 at 09:42:22PM +0100, Gerald Pfeifer wrote:
>
>> > will become invalid and I will laugh evilly as people try in vain to
>> > reach you.
>> 
>> Perhaps we ought to remove the part about laughin evilly?  Not all (new)
>> contributors might grok this kind of humor...
>
>
>I know it's very English-centric, but I think it's imperative we
>keep this.  There's so little humor on the site as it is.  Anyone
>who can push a patch past the oft-obstinate gcc and gdb patch
>approval processes MUST have a sense of humor to make it this far. :-)

I agree.  I hate to drop the humor on the off chance that someone might
be confused.  I haven't heard a single complaint about it, fwiw.

>> >     Host gcc.gnu.org
>> > 	Protocol 1
>> 
>> There's a typo here, but in general: Do we still have the Protocol 1
>> requirement?  (I have been using Protocol 2 for several months with
>> gcc.gnu.org, not the least because it's more secure.)
>
>
>IIRC it's just a matter of someone upgrading the web form scripts to 
>accept the id_dsa.pub style keys.  We switched from the last gratis
>protocol-1-only ssh to OpenSSH long ago.  Chris has posted on this
>topic in the past, but I think that's the gist of it.

This was one of the things I planned on changing after the new system
was set up.  I won't cry if someone beats me to it, though.

cgf

Re: Welcome to gcc.gnu.org

[Jason Molenda]

On Wed, Jan 22, 2003 at 09:42:22PM +0100, Gerald Pfeifer wrote:

> > will become invalid and I will laugh evilly as people try in vain to
> > reach you.
> 
> Perhaps we ought to remove the part about laughin evilly?  Not all (new)
> contributors might grok this kind of humor...


I know it's very English-centric, but I think it's imperative we
keep this.  There's so little humor on the site as it is.  Anyone
who can push a patch past the oft-obstinate gcc and gdb patch
approval processes MUST have a sense of humor to make it this far. :-)



> >     Host gcc.gnu.org
> > 	Protocol 1
> 
> There's a typo here, but in general: Do we still have the Protocol 1
> requirement?  (I have been using Protocol 2 for several months with
> gcc.gnu.org, not the least because it's more secure.)


IIRC it's just a matter of someone upgrading the web form scripts to 
accept the id_dsa.pub style keys.  We switched from the last gratis
protocol-1-only ssh to OpenSSH long ago.  Chris has posted on this
topic in the past, but I think that's the gist of it.


J

Re: Welcome to gcc.gnu.org

[Gerald Pfeifer]

(Some notes regarding our welcome message for new accounts.)

On Wed, 22 Jan 2003 root@sources.redhat.com wrote:
> Your account is now active, the login name is reichelt@gcc.gnu.org.
> [...]
> If your involvement with the project ends at some point, the mail address
> will become invalid and I will laugh evilly as people try in vain to
> reach you.

Perhaps we ought to remove the part about laughin evilly?  Not all (new)
contributors might grok this kind of humor...

> You should now have write access to the gcc repository with
> SSH+cvs.  Here are lots of details about how to do things.

s/gcc/GCC/  s/cvs/CVS/

> Regarding SSH:  By default, gcc.gnu.org uses ssh protcol 1.  If you
                                                   ^^^^^^^^^
> have keys in your .ssh directory which will also work with protocol 2,
> you will need to add the following lines to your a .ssh/config
> directory:
>
>     Host gcc.gnu.org
> 	Protocol 1

There's a typo here, but in general: Do we still have the Protocol 1
requirement?  (I have been using Protocol 2 for several months with
gcc.gnu.org, not the least because it's more secure.)

Gerald

Re: Welcome to gcc.gnu.org

[Gerald Pfeifer]

On Sun, 11 Mar 2001, Craig Rodrigues wrote:
> This gives me access to GCC CVS, but how do I get access to GNATS?

Overseers, I have taken care of that.

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

Re: Welcome to gcc.gnu.org

[Craig Rodrigues]

Hi,

This gives me access to GCC CVS, but how do I get access to GNATS?

Thanks.

-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@mediaone.net          

On Wed, Feb 28, 2001 at 03:46:10AM -0000, root@sourceware.cygnus.com wrote:
> Your account is now active, the login name is rodrigc@gcc.gnu.org.
> Mail sent to that address is forwarded to rodrigc@mediaone.net.  This
> forwarding is a convenience so that people who reply directly to CVS
> commit mail notes will not get a bounce--publicize it at your own risk.
> If your involvement with the project ends at some point, the mail address
> will become invalid and I will laugh evilly as people try in vain to
> reach you.
> 
> You should now have write access to the gcc repository with
> SSH+cvs.  Here are lots of details about how to do things.
> 
> You don't have general shell access, just CVS remote access.  Just about
> everything can be done via CVS.  If there is some special requirement
> that you have where you need shell access, talk to your project's lead
> and have them talk to overseers@gcc.gnu.org.  In special cases,
> we can be flexible on this requirement.
> 
> 
> 
> CVS  CVS is used for revision control.  If you are not familiar with CVS,
>      you have some reading to do.  http://www.cyclic.com/ is the central
>      source for all things CVS.  http://www.cyclic.com/cvs/info.html has
>      various information.  I don't see any simple introductions on using
>      CVS, so ask if you have questions.  The most important thing is this:
>      When you want to do a check-in of some change, do it like this:
> 
>      % cvs update
>      % cvs diff      # carefully verify what you're about to check in!
>      % cvs commit
> 
>      All of the sources are under CVS.  You have write access to the
>      files in your repository.  Check them out like this:
> 
>      export CVS_RSH=ssh
>      cvs -z9 -d :ext:rodrigc@gcc.gnu.org:/cvs/gcc co gcc
> 
>      After you've checked out some files, you won't need to specify the
>      CVSROOT (-d) again, it will be picked out of the CVS control files
>      (the CVS/Root file).  You will need to include the -z9; you can put
>      it in your $HOME/.cvsrc file ("cvs -z9") or add it to your command
>      line whenever you're doing CVS operations.
> 
>      If you're going over a modem, you'll definitely want to get this
>      as compressed as possible.
> 
>      To avoid the nuisance of having to supply your passphrase for each
>      operation, you may want to use ssh-agent(1) followed by ssh-add(1)
>      and entering your passphrase once for all.  Either start your
>      session as a child of ssh-agent or run it as a demon and set the
>      values of the environment variables SSH_AUTHENTICATION_SOCKET and
>      SSH_AGENT_PID in each relevant process to what ssh-agent prints
>      when it starts.  To avoid messages about (lack of) X11 forwarding,
>      put in your $HOME/.ssh/config and entry like:
> 
>         Host gcc.gnu.org
>         ForwardX11 no 
> 
> CVS COMMIT MESSAGES
>      You can get e-mail notifications for when things are checked in to
>      your group's repository.  There are two notification mailing lists,
>      one for the web pages for your project and one for the project
>      source files.  To subscribe to your source-file-notification list,
>      send a message to
> 
>          gcc-cvs-subscribe@gcc.gnu.org
> 
>      To get on a digest of the above list (get one note a day), send a 
>      note to 
> 
>          gcc-cvs-digest-subscribe@gcc.gnu.org
> 
>      The body/Subject are ignored in these messages.  The From: address
>      is the one you a requesting to subscribe.  To request an arbitrary
>      address be subscribed, say foo@bar.com, send a note like this:
> 
>          gcc-cvs-subscribe-foo=bar.com@gcc.gnu.org
> 
>      If your project has a web page, then there is a second mailing
>      list for notifications about changes to them.  The addresses are
>      just like the above ones except they include "-webpages" after the
>      project name.  For instance,
> 
>          gcc-webpages-cvs-digest-subscribe@gcc.gnu.org
> 
> 
>      If this is all a little confusing, just use the all-doing 
>      auto-subscriber at
>         http://gcc.gnu.org/ml/lists.html#faqs
> 
> CVSWEB You can browse changes that are being made to the CVS repository by
>      going to
> 
> 	http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc?cvsroot=gcc
> 
> HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
>      also under CVS.  You can create a home page (if one doesn\'t already
>      exist) for gcc by putting files in the htdocs/ directory of
>      your CVS repository.  They will appear instantly (within three or
>      four seconds, anyway) at http://gcc.gnu.org/gcc/
> 
> If anything is unanswered, please ask.