similar to: rsync with ssh mode vs. chroot

Hi, I want to backup my system via rsync over ssh, but login is *not* permited! According to the sshd_config man page, I need to set PermitRootLogin to forced-commands-only. In order to run follow command, how to set command option in authorized_keys? # rsync -avz server:/etc /backup Best Regards! Jacky Kim . >On Thu, Sep 09, 2004 at 06:03:49PM +0800, Jacky Kim wrote: >> If

Hi, all: The follow parameters work well in samba 2.2.8a, But I updated samba from 2.2.8a to the latest samba 3.0.5 , I can't write 'test' share! What is the ploblem? [test] path = /pub/test force user = abc write list = jacky valid users = jacky,abc create mode = 0664 directory mode = 0775 Best Regards! Jacky Kim .

Hi, all: I want to check small files' property(such as date, path, and so on) frequently. The files are stored in netwrok driver and their sizes vary from 2KB to 5KB. I found that Windows 2K outperform Linux/Samba very much after I campared the bench results. I am very confused about it and who can explain it? The computers' configurations are as follows: 1. PC Client It

When use rsync with daemon mode, how to permit user from using rsync via remote shell mode? Thanks very much! Best Regards! Jacky Kim .

If the shell of user alpha is /sbin/nologin When use rsync with ssh mode, is it possible for alpha to use rsync to backup data? I don't permit alpha to login the backup server. Thanks very much! Best Regards! Jacky Kim .

When I ssh-keygen a passwordless key pair for root and give the public key to openssh server(sshsrv), then it is ok to # ssh root@sshsrv But when I generate a password key pair for root and give the public key to openssh server(sshsrv), then I fail to # echo "rootpasswd" | ssh root@sshsrv and get the follow message: Pseudo-terminal will not be allocated because stdin is not a

Hi, all: I am using Samba 3.0.5 with patch at http://samba.org/~jerry/patches/post-3.0.4/. But I found the follow messages in samba log: =============================================================== [2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1398) PANIC: internal error [2004/07/29 01:01:57, 0] lib/util.c:smb_panic2(1406) BACKTRACE: 3 stack frames: #0 smbd(smb_panic2+0xef)

> Klaas Jan Wierenga wrote: > > > I'm not using yp directory listings, but I can guess why it is not > > working. > > You're probably missing the libcurl.so library in your chroot jail > > directories. Here's the listing of files I have in the chroot jail: > > Definitely not, I rebuilt the whole lib structure i got from > ldd in my chroot But

I have a RedHat 6.0 x86 server which is serving a number of minor things, which I wish to add shell access to. I'm currently running sshd and am quite happy with it, the exceptiong being that I am unable to make sshd perform a chroot for shell account users. I have been reading man pages and howto's, many of which discuss sshd or chroot, but never the two together. Is this not an

Hello, I'm new to the list, but hopefully I've done enough digging around that I don't get yelled at too terribly ;) We're looking to implement a chrooted environment for allowing users to scp files from servers. That's basically the only functionality that we need in this case. We're looking to chroot the user and/or remove any chance that the account can login via

Please post to the mailing list the next time Ralf. I'm not using yp directory listings, but I can guess why it is not working. You're probably missing the libcurl.so library in your chroot jail directories. Here's the listing of files I have in the chroot jail: -----%< cut here > ls -R .: admin etc lib opt usr var web ./admin: listclients.xsl listmounts.xsl

Hello - I am trying to set up a ssh chroot account on a Red Hat Enterprise Linux 5 server. I have my jail set up and have copied over a selection of commands and their libraries. I have also created a / dev and some devices. As part of that, I had to create a /dev/pts directory to handle the terminals. However, when I try to connect as the chrooted user, I get the following error:

Hi, I failed to mount samba 3.0.6's share with NULL password: # mount -t smbfs -o username=alpha,password="" //192.168.3.101/pub /mnt And what samba log say: [2004/08/24 16:30:08, 2] auth/auth.c:check_ntlm_password(312) check_ntlm_password: Authentication for user [alpha] -> [alpha] FAILED with error NT_STATUS_WRONG_PASSWORD But it is ok when using samba 2.2.8a! Best

I just downloaded the bind-chroot rpm and looked into it with Archive manager (so I am lazy), and no files, just the chroot tree. I am assuming there is some script that Archive manager does not show, or I am just missing it, because the ROOTDIR= did get added to /etc/sysconfig/named (and the one in the bind rpm is without this line). Just interesting that if you chroot, you are expected to

I setup a ssh chroot jail following this[1] guide. It works for my user to login, use ls and use scp which is all I really want. I do have a problem I cannot solve: when connected and navigating the filesystem, the backspace key actually moves the cursor forward and does not delete what I type. I may have found a hint from some googling that readline will read in /etc/inputrc on login but if

As I can seen, there is the bind-chroot glue package, but is there a postfix-chroot.rpm glue ? I have looked for it, but I think there is not. If there is not, what is your opinion about creating one ? Thanks -- Vilela -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Damien, Thank you. I read the rationale. Just to summarize, a user writeable chroot target is considered dangerous if: 1) the user has another way of gaining non-chrooted access to the system 2) is able to create hardlinks to setuid-binaries outside of the chroot tree 3) there are bugs somewhere that allow privilige escalation or remote execution of other programs While all these

Hi All, I'm migrating a CentOS 6 bind instance (chrooted) to a CentOS 7 box and am curious of people's opinions on chrooting vs selinux as a way of securing bind. The bind-chroot on CentOS 7 also comes with a script (/usr/libexec/setup-named-chroot.sh) that sets up the much maligned systemd and, through bind mounts, creates and extra level of chroot hierarchy giving:

Hi, I need to make a custom code change in sftp-server module to copy the received file outside the chroot-setup. I am trying to chroot repeatedly to get physical root directory and the copy received file to a directory outside chrooted directory. The children processes are owned by the sftp-user and so, sftp child process does not have permission to escape out of chroot. Is there a simple way

-----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Rainer Duffner Sent: Samstag, 21. Oktober 2017 00:41 To: CentOS mailing list Subject: Re: [CentOS] scp setup jailed chroot on Centos7 > Am 20.10.2017 um 15:58 schrieb Adrian Jenzer <a.jenzer at herzogdemeuron.com>: > > Dear all > > I'm looking for instructions on how to setup a