[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    [FreeNX-kNX] Allow !M connection only and not regular ssh
From:       jonachen () cisco ! com (Jonathan Chen)
Date:       2005-04-25 21:57:42
Message-ID: 200504252157.j3PLviKx022367 () sj-core-2 ! cisco ! com
[Download RAW message or body]

Ok, I'm trying to test out this function...  The node.conf file says to add
nx into the wheel for "su -c"

# This adds SU to the possible authentication methods. For it to work the
# "nx" user must be in the wheel (RedHat, Fedora) or the users group (SUSE)
# and the user logging in must have a valid shell that accepts the -c
# parameter.
ENABLE_SU_AUTHENTICATION="1"

sudo gpasswd -a nx wheel

And I would get the result below...

wheel:x:10:root,nx

I have not done the sshd_config change yet but wanted to just test out if
"su" works 1st before I add the line

AllowUsers root nx

In sshd_config.   When using the windows NX client, it "freezes" at 

NX> 102 Password: 
Auth method: su 

Am I missing something?

FreeNX 0.3.1 on RHEL 3.

> 
> Message: 9
> Date: Sat, 23 Apr 2005 06:26:49 +0200
> From: Blindauer Emmanuel <freenx at mooby.net>
> Subject: Re: [FreeNX-kNX] Allow !M connection only and not regular ssh
> To: freenx-knx at kde.org
> Message-ID: <200504230626.49810.freenx at mooby.net>
> Content-Type: text/plain;  charset="iso-8859-1"
> 
> Le Saturday 23 April 2005 01:46, Jonathan Chen a icrit :
> > Hi all,
> >
> > I'm wondering if anyone tried to have a setup where it will only 
> > accept !M login over ssh and not let that user in if they 
> use regular 
> > ssh client to logon?
> 
> yes:  in sshd : allow nx from all and all from localhost 
> AllowUsers nx@*.*.*.*  *@::ffff:127.0.0.1 *@127.0.0.1 
> 
> (2 entries for localhost (ipv6/ipv4)
> 


[prev in list] [next in list] [prev in thread] [next in thread]