Jim,
my bad. Poor Mike, this is gonna hurt and to not much avail. Btw.,
there is a sort of a workaround for the network sniff insecurity issue -
use encrypting intel nics on the server and in the clients. a friend of
mine who works for an "unnamed" military contractor insists that when
handled right they provide a very high level of security. julius
On Fri, 31 Jan 2003 [EMAIL PROTECTED] wrote:
> On Fri, 31 Jan 2003, Julius Szelagiewicz wrote:
> > Mike,
> > rush, or no rush, you still have to generate keys and configure
> > sshd. thta said, "service sshd start"
>
> He wants to run sshd on the client. BUT, it doesn't exist on the
> client, so rush or no rush, this is gonna take awhile.
> > On Fri, 31 Jan 2003, Mike Eggleston wrote:
> > > What do I turn on to get sshd running so that I can
> > > ssh to the boxes instead of rsh? I can look this
> > > up, but I'm in a rush.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
