From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) by sourceware.org (Postfix) with ESMTPS id 2EC783858D28 for ; Mon, 11 Oct 2021 01:46:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2EC783858D28 Received: by mail-wr1-x42f.google.com with SMTP id o20so50640518wro.3 for ; Sun, 10 Oct 2021 18:46:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=iq2nv8WzS3H3a2lWb12OwGLHZccs1eFws4sJlYweAbI=; b=VO2eWONez/NDKGSQdEjM28pwPeWUYSc7qE/wVdP49FN4SdEiv4eZQIkmYIjaAiixPl Q8pYcLWKY3WxrQ0NnZ4xnclH10DhwO7j15Ulg4TryAcO+CAGxgiI8ohjHy9dOrGmfi6V VaH9Al6OvOzRmeO5DMNfhhBI9stFzsGq4KBxPtJCIzEqa7pcoVs2EYVh7JbTWMsUecI2 uhdwutVs0INm5vs7xDtUvD1M4+JgDikM+5C2Ozo+9H8yB7MRRalyCpL/9Pmuj/r4sM5x QWMhCD78Un8Qfo1fq9jyBKIs6SX0bUCQ79YcRvi4oNBcn3ASEhrvh7+4XYHEA+O4aUNa cyfQ== X-Gm-Message-State: AOAM531olXaJKaJfZSrzEwN+N/I/YfbzHeiEI25MG+dN1e6r6FJlKgyn 5wzNhWlkrFpnT9WLvL60pTsYCrXkaSu7SF4kgMJPK0a6oEvinQ== X-Google-Smtp-Source: ABdhPJyUnYI7NY/IwYK6gwyx3KhuBFrXe647Z/eoiugi/UO8s041tO0YQ07puMjdM8gr2eo4PyFGI51HPxLfhH9vi+A= X-Received: by 2002:adf:a505:: with SMTP id i5mr21479758wrb.38.1633916782872; Sun, 10 Oct 2021 18:46:22 -0700 (PDT) MIME-Version: 1.0 From: Eric Gallager Date: Sun, 10 Oct 2021 21:46:11 -0400 Message-ID: Subject: ssh keys To: overseers@gcc.gnu.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2021 01:46:25 -0000 Hello GCC Overseers, it's Eric Gallager here, and I'd like to get back to committing to the GCC project again. The last time I committed was back in the SVN days, and it was from a different computer than I currently use, and I'm afraid my ssh keys from the old computer got lost in the migration process somehow, so if I'm going to get back to committing again, I'm going to need to be able to use a new ssh key (since I haven't been able to find my old one). My "@gcc.gnu.org" email address is egallager@gcc.gnu.org (it forwards to this address egall@gwmail.gwu.edu that I'm currently writing from), and I have mentioned this issue with my keys with that account on Bugzilla, for example, here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56604 My original sponsor when I first applied for commit access was David Malcolm, and I still have a copyright assignment on file with the FSF (which I visited in person to deliver), so you can contact them if necessary. Also I was asking about this issue on the #gcc IRC channel on oftc.net, where Iain Sandoe recommended I email the overseers about it, so he can vouch for me, too. This is also something I've mentioned on my Twitter account: https://twitter.com/cooljeanius/status/1413700314398666753?s=21 Let me know if there are any other ways I can verify my identity in order to get my ssh keys switched, and I apologize for my scatterbrainedness in letting this situation arise. Thanks, Eric Gallager