From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4301 invoked by alias); 2 Apr 2004 18:15:33 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 4292 invoked from network); 2 Apr 2004 18:15:31 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 2 Apr 2004 18:15:31 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i32IFVjj020872 for ; Fri, 2 Apr 2004 13:15:31 -0500 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i32IFVj18755 for ; Fri, 2 Apr 2004 13:15:31 -0500 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id i32IFUf7004198 for ; Fri, 2 Apr 2004 13:15:30 -0500 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 82CEA80008E for ; Fri, 2 Apr 2004 13:15:30 -0500 (EST) Received: from toenail.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by toenail.toronto.redhat.com (8.12.10/8.12.5) with ESMTP id i32IFUHl031031 for ; Fri, 2 Apr 2004 13:15:30 -0500 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.12.10/8.12.10/Submit) id i32IFUIB031029 for overseers@sources.redhat.com; Fri, 2 Apr 2004 13:15:30 -0500 Date: Fri, 02 Apr 2004 18:15:00 -0000 From: "Frank Ch. Eigler" To: overseers@sources.redhat.com Subject: Re: Error trying to get CVS write access via web-form Message-ID: <20040402181529.GM26117@redhat.com> References: <20040402155707.GC1144@coc.bosbc.com> <20040402161740.GH26117@redhat.com> <20040402164058.GH1144@coc.bosbc.com> <20040402164511.GI26117@redhat.com> <20040402165750.GJ1144@coc.bosbc.com> <20040402170838.GJ26117@redhat.com> <20040402172332.GA6781@coc.bosbc.com> <20040402172928.GL26117@redhat.com> <20040402174003.GA7172@coc.bosbc.com> <20040402180558.GA7424@coc.bosbc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Rmm1Stw9KgbdL9/H" Content-Disposition: inline In-Reply-To: <20040402180558.GA7424@coc.bosbc.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2004-q2/txt/msg00018.txt.bz2 --Rmm1Stw9KgbdL9/H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 344 Hi - > [...] > Is there a way to get ssh to tell us if the key looks right? That's > probably the best way to verify keys. [...] Or an even tougher-love approach would be to force new account holders to log in using the putative key within some time limit after initial account activation, to prove they hold a matching private key. - FChE --Rmm1Stw9KgbdL9/H Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAba3BVZbdDOm/ZT0RAnOtAJ0eN6qUC0C4QlaLGt0Y8twhSoItBgCeIUjw D3RYHGClUQvPY6G/nSF0P0o= =OLVS -----END PGP SIGNATURE----- --Rmm1Stw9KgbdL9/H--