From: Kalkin Sam <mail@kalkin.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: creating ssh account without directory browsing
Date: Sun, 5 Sep 2010 18:55:56 +0200 [thread overview]
Message-ID: <slrni87iss.kia.mail@kalkin.de> (raw)
In-Reply-To: 4C7A37CC.7000009@googlemail.com
Hi,
Young padawan Tamer Higazi <th982a@googlemail.com> spoke:
> Everytime I uncomment: "ChrootDirectory /work" and I try to connect, I
> receive this message on the console:
>
> Write failed: Broken pipe
>
>
> Any ideas?!
Yes RTFM and Google :)
man sshd_config and look at ChrootDirectory entry:
<cite> All components of the pathname must be root-owned directories
that are not writable by any other user or group. After the chroot,
sshd(8) changes the working directory to the user's home
directory</cite>
Here an Ubuntu forum which handles the same problem:
http://ubuntuforums.org/showthread.php?t=1482005
kalkin-
--
Paranoid sein heisst frei sein
(Hal Faber)
prev parent reply other threads:[~2010-09-05 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 8:36 [gentoo-user] creating ssh account without directory browsing Tamer Higazi
2010-08-22 9:27 ` Alex Schuster
2010-08-22 12:31 ` Giampiero Gabbiani
2010-08-22 14:49 ` Mick
2010-08-22 16:27 ` Alan McKinnon
2010-08-22 18:40 ` [gentoo-user] " Kalkin Sam
2010-08-29 10:34 ` Tamer Higazi
2010-09-05 16:55 ` Kalkin Sam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrni87iss.kia.mail@kalkin.de \
--to=mail@kalkin.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox