Well, I seem to have resolved most of this. In the end I had to
create a separate logical link for the chrooted users' home
directories that pointed back to their actual directory. It sounds
confusing because it is.
I first tried this in sshd_conf
ChrootDirectory %h
and in ~/%h I had creat
James B. Byrne wrote:
So, before I go messing around moving files I would some information
from you as tio what I have overlooked. Do I need to move something
like etc/passwd and /etc/group into the chroot/etc?
You haven't said anything about the process you used, so it's hard to
say what y
James B. Byrne wrote:
>
> On Mon, July 6, 2015 15:47, m.r...@5-cent.us wrote:
>> James B. Byrne wrote:
>>> We have a requirement to allow ssh access to a server in order to
>>> provide a secure link to one of our legacy systems. I would like to
>>> chroot these accounts.
>>>
>>> I have this workin
On Mon, July 6, 2015 15:47, m.r...@5-cent.us wrote:
> James B. Byrne wrote:
>> We have a requirement to allow ssh access to a server in order to
>> provide a secure link to one of our legacy systems. I would like to
>> chroot these accounts.
>>
>> I have this working except for one small detail,
On Jul 6, 2015, at 2:49 PM, James B. Byrne wrote:
> However, instead of getting the prompt defined in their
> .bash_profiles we see this:
>
> -bash-4.1$
>
> when we are expecting this:
>
> [username@hostname dir]$
>
> So, before I go messing around moving files I would some information
> from
James B. Byrne wrote:
> We have a requirement to allow ssh access to a server in order to
> provide a secure link to one of our legacy systems. I would like to
> chroot these accounts.
>
> I have this working except for one small detail, the user's prompt in
> the ssh session. Each user has their
6 matches
Mail list logo
