[FreeNX-kNX] Re: getting nx to work with non-standard PAM setup

[Alex Aminoff]

On Tue, 1 Feb 2011, Alex Aminoff wrote:
> On Fri, 28 Jan 2011, chris at ccburton.com wrote:
>> Alex Aminoff <aminoff at nber.org> wrote on 28/01/2011 13:23:40:
>> > On Thu, 27 Jan 2011, chris at ccburton.com wrote:
>> >
>> > > The logging in of the user to FreeNX is done with an "expect" script
>> which
>> > > you can test yourself,
>> > >
>> > > eg  run:-
>> > >
>> > >      /usr/bin/nxnode-login ssh aminoff 22 /usr/bin/nxnode --check
>> > >
>> > > The script waits with NO prompt for you to enter your password.
>> >
>> > Thank you so much! That is exactly what we need to figure this all out!
>> 
>> Let us know how you get on !!
>
> This appears to work.
>

A separate problem. I am using nx to alternately connect to a server that 
has a pretty standard ssh config and one that uses our special phone auth. 
It appears that nx tries to ssh to my username from user nx at localhost 
(127.0.0.1). However, my home directory, including 
~aminoff/.ssh/known_hosts, is NFS-shared between the servers. So ssh 
writes a host key for 127.0.0.1 on one of the servers, and then when I try 
on the other one ssh complains of a changed host key. Again, this is 
something that can be avoided by sshing direct as the user, which I will 
try next.

But it seems like this would be a common problem. Is using nx to 
connect to multiple servers that share homedirs by nfs not a common usage 
pattern?

  - Alex