a> Restricting users to their home directory.
Sorry, not possible with plain UNIX shells. Perhaps you could make a menu
system and have them use that instead?
b> Restricting host access.
Method 1:
Build SSH with tcp wrapper (aka libwrap) support. If you don't have or
know about tcp wrappers, find them (they're by a fellow named Wietese
Venema, though my spelling may be off) and install at least the libwrap.a
library file somewhere (I put it in /usr/local/lib)
Method 2:
Check out the AllowHosts and DenyHosts directives. These go into your
sshd2_config file and will provide IP-based access control. It's not as
smooth as TCP wrappers, but it does work well.
c> Login names / shells
The same login and password they're currently using will work. The same
shell will work.
d> Clients for Windows.
My favorite is VanDyke SecureCRT 3.0
There's also F-Secure SSH2 and others.
--
Gregor Mosheh
[EMAIL PROTECTED]
Systems Admin, Humboldt Internet
707.825.4638
On Mon, 24 Jan 2000, Rajagopalan, Srikanth wrote:
> Hi All
>
> Can anyone please help me in setting sshd2 for my environment?
>
> I have downloaded and installed sshd2 on our Solaris 2.6 systems. I don't
> know what to
> do next? I thought of setting secured shell account to our customers
> without compromising
> on our security.
>
>
> How to give them secured access to their local directories? what user-login
> shell do i have to
> give them? I know their IP-address and domain name from which they are
> connecting
> to our solaris server. How to setup host restrictions on per user basis?
> How to give them secured ftp access? Most of our customers are windows
> 95/NT based
> users.
>
>
> Please help me in knowing what to do next?
>
> Thanks in advance
> Srikanth
>
> --Srikanth.R
> 617.856.1049 (work)
>
>
>
>
>
>
