<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9"> </HEAD> <BODY> Hi, guys. I just uploaded a 0.6 version of the NX_LTSP package which starts to address this issue. Basically, upon launch of the screen script, it will copy the appropriate key for the appropriate server specified by "session_name". Instead of saving the file as client.id_dsa.key, save it as client.id_dsa.key.<session_name> When the screen script is ran, it will copy the appropriate file to client.id_dsa.key. Specify session_name with the "-n <session_name>" flag. The default session_name is "session", so if you only have one server, please save the key as client.id_dsa.key.session . Let me know if this addresses the issue. The only minor pain that I can envision at this moment is that if 2 sessions start upon boot, one session has to be logged into first, and then the second has to be restarted with ctrl-alt-backspace. I will work to try and get the copying of the key to happen after login instead, which would fix this. Cheers, -Gideon On Thu, 2005-02-03 at 10:31, Mark Gumprecht wrote: <BLOCKQUOTE TYPE=CITE> <PRE>I have found a few posts that talk about replacing the server key after the nxsetup has run. But none say where the key is. Is it the server.id_dsa.pub.key in the /var/lib/nxserver/nxhome/.ssh/ directory? Mark cliebow@downeast.net wrote: >mark i wrote a stupid little script to swap the keys back and forth..so the >keys here are clien.id_dsa.key.su for surry client.id_dsa.key.ca for cave >hill..the script overwrites the existing client.id_dsa.key with the right one.. >i need to find out how to sync the keys for all servers so (for this use) >theyuy are the same.,.chuck > > > >>I finally got in, Missed a step in the instructions, 4 times, Duh! But >>something else has dawned on me. If you have multiple ltsp machines, >>Does your method below change the requirement for transferring the key >>from server to client by scp method in the NX/share? Went you try the >>test drive on nomachine.com, you do not have to transfer the key to the >>share directory. That's what I'm shooting for. >>Mark >> >>Trond Mæhlum wrote: >> >> >> >>>I did this, roughly from memory, to solve the same problem: >>> >>>rm -rf /var/lib/nxserver/nxhome/.ssh/ >>>mkdir /var/lib/nxserver/nxhome/.ssh/ >>>chmod 700 /var/lib/nxserver/nxhome/.ssh/ >>>nxsetup --setup-nomachinekey >>>nxsetup --force --setup-nomachinekey >>> >>> >>> >>> >>> >>-- >>Mark Gumprecht >>Data Systems Specialist >>MSAD3 >>Unity, Maine >>gumprechtm@msln.net >> >>_______________________________________________ >>K12OSN mailing list >>K12OSN@redhat.com >><A HREF="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</A> >>For more info see <<A HREF="http://www.k12os.org">http://www.k12os.org</A>> >> >> >> > > >--------------------------------------------- >This message was sent from Downeast.Net. ><A HREF="http://ellsworthme.com/">http://ellsworthme.com/</A> > > >_______________________________________________ >K12OSN mailing list >K12OSN@redhat.com ><A HREF="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</A> >For more info see <<A HREF="http://www.k12os.org">http://www.k12os.org</A>> > > ></PRE> </BLOCKQUOTE> <PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> <PRE>-- -------------------------------------------------------- Gideon Romm | Product R&D gideon@symbio-technologies.com Symbio Technologies o:(914) 576-1205 134 North Ave, Suites E&F f:(914) 576-0944 New Rochelle, NY 10801 c:(914) 774-4691 www.symbio-technologies.com www.thesymbiont.com</PRE> </TD> </TR> </TABLE> </PRE> </BODY> </HTML>