From mi@aldan.algebra.com  Fri May  4 09:22:38 2001
Return-Path: <mi@aldan.algebra.com>
Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224])
	by hub.freebsd.org (Postfix) with ESMTP id 11A6137B424
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  4 May 2001 09:22:33 -0700 (PDT)
	(envelope-from mi@aldan.algebra.com)
Received: (from mi@localhost)
	by aldan.algebra.com (8.11.3/8.11.3) id f44GOZ723909;
	Fri, 4 May 2001 12:24:35 -0400 (EDT)
	(envelope-from mi)
Message-Id: <200105041624.f44GOZ723909@aldan.algebra.com>
Date: Fri, 4 May 2001 12:24:35 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
Reply-To: mi@aldan.algebra.com
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: sshd may mis-parse the authorized_keys file
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         27080
>Category:       bin
>Synopsis:       sshd may mis-parse the authorized_keys file
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 04 09:30:00 PDT 2001
>Closed-Date:    Thu Jul 12 16:48:37 PDT 2001
>Last-Modified:  Thu Jul 12 16:50:01 PDT 2001
>Originator:     Mikhail Teterin
>Release:        FreeBSD 4.3-BETA i386
>Organization:
Virtual Estates, Inc.
>Environment:
FreeBSD raidbox.privatelabs.com 4.3-BETA FreeBSD 4.3-BETA #0: Tue Apr 10 20:30:55 EDT 2001     mi@minime.privatelabs.com:/raid/src/sys/compile/RAIDBOX  i386

>Description:

	I have some keys in the authorized_keys file with some limitational
	flags:
	no-pty,no-port-forwarding,no-agent-forwarding 1024 35 ..key...

	If add another key _after_ this one, the flags seem to apply to it
	too, even though its line does not have them. no-pty is the most
	noticable one.

>How-To-Repeat:

	Put a couple of keys with no-pty,no-port-forwarding and
	no-agent-forwarding flags in front of your regular keys.
	See, if you can still login normally.

>Fix:

	Make sure the keys with the special flags are at the bottom of
	the file. Not a complete work-around, since the flags may be
	mixed for different keys.
>Release-Note:
>Audit-Trail:

From: Kris Kennaway <kris@obsecurity.org>
To: Mikhail Teterin <mi@aldan.algebra.com>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/27080: sshd may mis-parse the authorized_keys file
Date: Sat, 5 May 2001 22:31:00 -0700

 --G4iJoqBmSsgzjUCe
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Fri, May 04, 2001 at 12:24:35PM -0400, Mikhail Teterin wrote:
 
 > 	I have some keys in the authorized_keys file with some limitational
 > 	flags:
 > 	no-pty,no-port-forwarding,no-agent-forwarding 1024 35 ..key...
 >=20
 > 	If add another key _after_ this one, the flags seem to apply to it
 > 	too, even though its line does not have them. no-pty is the most
 > 	noticable one.
 
 Could you bring this up with the OpenSSH developers, please?  OpenSSH
 isn't developed separately in FreeBSD except for a few local changes.
 
 Kris
 
 --G4iJoqBmSsgzjUCe
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.5 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE69OGTWry0BWjoQKURAhogAJ0Z0vJVc41XIzBLAVyQq+ZsA7sQBACfUb7f
 1BLCztFV5I9Pxk+uq92F0Wk=
 =yfOr
 -----END PGP SIGNATURE-----
 
 --G4iJoqBmSsgzjUCe--
State-Changed-From-To: open->closed 
State-Changed-By: kris 
State-Changed-When: Thu Jul 12 16:48:37 PDT 2001 
State-Changed-Why:  
FreeBSD does not maintain OpenSSH separately to the main 
development effort.  Please submit your bug report there. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27080 

From: Kris Kennaway <kris@obsecurity.org>
To: Mikhail Teterin <mi@aldan.algebra.com>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/27080: sshd may mis-parse the authorized_keys file
Date: Thu, 12 Jul 2001 16:48:33 -0700

 --fOHHtNG4YXGJ0yqR
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Please take this up with the OpenSSH developers.  Thanks.
 
 Kris
 
 On Fri, May 04, 2001 at 12:24:35PM -0400, Mikhail Teterin wrote:
 >=20
 > >Number:         27080
 > >Category:       bin
 > >Synopsis:       sshd may mis-parse the authorized_keys file
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:       =20
 > >Keywords:      =20
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Fri May 04 09:30:00 PDT 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Mikhail Teterin
 > >Release:        FreeBSD 4.3-BETA i386
 > >Organization:
 > Virtual Estates, Inc.
 > >Environment:
 > FreeBSD raidbox.privatelabs.com 4.3-BETA FreeBSD 4.3-BETA #0: Tue Apr 10 =
 20:30:55 EDT 2001     mi@minime.privatelabs.com:/raid/src/sys/compile/RAIDB=
 OX  i386
 >=20
 > >Description:
 >=20
 > 	I have some keys in the authorized_keys file with some limitational
 > 	flags:
 > 	no-pty,no-port-forwarding,no-agent-forwarding 1024 35 ..key...
 >=20
 > 	If add another key _after_ this one, the flags seem to apply to it
 > 	too, even though its line does not have them. no-pty is the most
 > 	noticable one.
 >=20
 > >How-To-Repeat:
 >=20
 > 	Put a couple of keys with no-pty,no-port-forwarding and
 > 	no-agent-forwarding flags in front of your regular keys.
 > 	See, if you can still login normally.
 >=20
 > >Fix:
 >=20
 > 	Make sure the keys with the special flags are at the bottom of
 > 	the file. Not a complete work-around, since the flags may be
 > 	mixed for different keys.
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 >=20
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-bugs" in the body of the message
 
 --fOHHtNG4YXGJ0yqR
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE7TjdQWry0BWjoQKURApw6AJ0QgyWSfoAXYxEJfcztGz5FnFYihQCePgTY
 k3EKNKYMEPry/RJfKiq+jXc=
 =zst8
 -----END PGP SIGNATURE-----
 
 --fOHHtNG4YXGJ0yqR--
>Unformatted:
