From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Jones Subject: Re: ssh in SLES10 SP1 RC2 Date: Wed, 30 May 2007 12:12:27 -0700 Message-ID: <20070530191226.GA4330@suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx2.redhat.com (mx2.redhat.com [10.255.15.25]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l4UJCubo016310 for ; Wed, 30 May 2007 15:12:56 -0400 Received: from mx1.suse.de (ns1.suse.de [195.135.220.2]) by mx2.redhat.com (8.13.1/8.13.1) with ESMTP id l4UJCGDG004053 for ; Wed, 30 May 2007 15:12:16 -0400 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Michael Folsom Cc: linux-audit@redhat.com, "Wieprecht, Karen M." List-Id: linux-audit@redhat.com On Tue, May 29, 2007 at 04:03:50PM -0600, Michael Folsom wrote: > Checked and SLES10/SLED10 SP1 rc2 and rc3 are both running openssh 4.2p1-18. > > Looks like monitoring logouts won't happen in Suse Enterprise land > till SSH get reved to a newer version! We added patches to generate the appropriate USER_LOGIN messages for SP1 into gdm, login and openssh. The other messages were handled via PAM. I'm not sure what the exact issue is as I missed the startt if the thread. As an aside it's not a matter of necessarily reving to a newer version, rather of backporting the necessary changes (unless they are no invasive that it requires moving forward to a new revision). We try to avoid upgrading package versions once we begin the release process, rather we cherrypick. We would have taken a bug report during the beta process and would have rolled the fix into the older version but it's too late now. Still, I'd recommend you file a bug in Novell bugzilla. Tony