similar to: No subject

> On 15 Jun 2017, at 19:29, Karl O. Pinc via rsync <rsync at lists.samba.org> wrote: > > On Thu, 15 Jun 2017 13:23:44 +0000 > just subscribed for rsync-qa from bugzilla via rsync > <rsync at lists.samba.org> wrote: > >> https://bugzilla.samba.org/show_bug.cgi?id=12819 >> >> --- Comment #7 from Ben RUBSON <ben.rubson at gmail.com> --- >

https://bugzilla.samba.org/show_bug.cgi?id=12817 Bug ID: 12817 Summary: [PATCH] Allow daemon itself to chroot Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

I am supporting a site that allows members to upload release files. I have inherited this site which was previously existing. The goal is to allow members to file transfer to and from their project area for release distribution but not to allow general shell access and not to allow access to other parts of the system. Currently rsync and old scp has been restricted using a restricted shell

Rsync team, and interested parties: i was attempting to get rsync to launch from tcpserver[0] (an inetd replacement from djb) and log to stderr for logging via multilog[1] (syslog replacement by djb) and i was unable to get it to log to stdout/ stderr at all. [0] http://cr.yp.to/ucspi-tcp/tcpserver.html [1] http://cr.yp.to/daemontools/multilog.html i have attached a patch that allows

On 12.11.23 03:52, Damien Miller wrote: > On Sat, 11 Nov 2023, Bob Proulx wrote: > >> I am supporting a site that allows members to upload release files. I >> have inherited this site which was previously existing. The goal is >> to allow members to file transfer to and from their project area for >> release distribution but not to allow general shell access and not

On Sat, 11 Nov 2023, Bob Proulx wrote: > I am supporting a site that allows members to upload release files. I > have inherited this site which was previously existing. The goal is > to allow members to file transfer to and from their project area for > release distribution but not to allow general shell access and not to > allow access to other parts of the system. > >

(I think the subject is quite descriptive; however for use-cases and details see bellow after the mention of the old conversation and the patch.) Searching the mailing list about this topic yields an old conversation about this from 2008: * https://lists.samba.org/archive/rsync/2008-November/022148.html * https://lists.samba.org/archive/rsync/2008-November/022150.html I'll quote

hello, i`m trying to use rsync via inetd and having problems. i`m getting 2009/06/15 18:25:29 [41082] name lookup failed for : ai_family not supported 2009/06/15 18:25:29 [41082] connect from UNKNOWN () when trying to write to rsync daemon via inetd. reading works fine. inetd.conf looks like this: rsync stream tcp nowait root /path/rsync rsync --daemon --log-file=/tmp/rsync.log

I'm trying to get over an exasperating problem with rsync 2.5.7, but I'm not making any headway. The nut of the problem is that the rsync daemon seemingly ignores the "syslog facility" configuration when running in standalone daemon mode, as opposed to being started with inetd. So, for example, if I have my configuration file with [global] pid file = /etc/rsync/rsyncd.pid

Scenario: I have a main website. I want to allow other people with web servers to use rsync to synchronize mirror copies of my website. When the mirror website uses rsync to connect to the server, how can it be sure that the server is not an IP spoofing impostor that is serving up altered files?

On Thu, 15 Jun 2017 13:23:44 +0000 just subscribed for rsync-qa from bugzilla via rsync <rsync at lists.samba.org> wrote: > https://bugzilla.samba.org/show_bug.cgi?id=12819 > > --- Comment #7 from Ben RUBSON <ben.rubson at gmail.com> --- > Note that my patch simply adds a sync() just after recv_files(), so > one sync() per connection, not per write operation. >

Greetings, Has anyone successfully compiled rsync 2.5.5 under Mac OS X (not Server), and actually have it work fully? I'm in a position where I'm trying to setup an automated nightly remote backup between and Cobalt Raq4 (running a variant of Redhat Linux) and a Mac running OS X 10.1.5 with the latest development tools installed. As has been pointed out previously on the list, one has

Hi, I can't figure out how to backup a tree with symlinks. I either get errors like rsync: open(rc2.d/S20inetd) failed!!: No such file or directory (2) or (with --safe-link on the client and "munge symlinks = yes" on the server): ignoring unsafe symlink "/etc/rc2.d/S20inetd" (in backups) -> "/rsyncd-munged/../init.d/inetd" What I am trying to do is

Hi, i have sporadic connection problems with my rsync server. I have _no_ firewall involved and there is _no_ max connections set. rsync on the clients is started from cron via a bash script. There's also no permission problem. rsyncd runs as daemon (is not started from inetd). It sometimes works, but every third or fourth rsync fails with this message: rsync: failed to connect to

rsync and ajug lists, been pulling my hair out on this one. i have some java code which uses the Process object to spawn an rsync connection in --daemon mode. the exact same command executes properly when run from outside java (i.e .on the command line) on osx. it also executes correctly from within java on linux using a similar jdk (sun 1.4.1 vs sun 1.4.2 for osx) here is example code:

yeah, i tried that already. specifcially, mine was: /* String cmd[] = new String[5]; cmd[0] = "/usr/local/bin/rsync"; cmd[1] = "--daemon"; cmd[2] = "--config=/Users/dlippolt/.azerup/rsyncd.conf"; cmd[3] = "--address=127.0.0.1"; cmd[4] = "--port=2873"; */ as an aside, i dont have my head fully wrapped around the real

Hello, we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon mode spawned by inetd (Solaris 5.8 Environment). /etc/services: rsync 1234/tcp #RSYNC daemon /etc/inet/inetd.conf: rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 . Alas, this does not seem to work, there is the following error message in the log file:

Salim: I suspect that if you check the timestamp, you'll find that that binding failure is left over from an earlier attempt, before you were properly configured. Your description of you inetd.conf/services setup sounds correct. Your commandline, though, shouldn't work. You name a directory as the source, but don't say to do its contents. However, I would expect an error from

Roger Marquis wrote: > [snip] > >It takes all of 2 seconds to generate a ssh 2 new session on a >500Mhz cpu (causing less than 20% utilization). Considering that >99% of even the most heavily loaded servers have more than enough >cpu for this task I don't really see it as an issue. > >Also, by generating a different key for each session you get better >entropy,

Sonu: I'm giving the whole history to the rsync list. If the tests i subscribed passed, yet you get that error, it's more in depth than i can go into. You've got 1 hour, let's hope somebody immediately recognizes the problem. I've got some ideas, but no time to explore any more for you. Gentlemen: does anybody see a quick resolution for Sonu? Looks like he's