similar to: Rsync 2.5.7 local buffer overflow

Hi all, My patch for supporting "Basic" HTTP Proxy Authentication has been updated for rsync 2.5.6 by Martin Ehmsen. The patch changes the interpretation of the RSYNC_PROXY environment variable so that the syntax user:pass@proxy.foo.com:port may be used instead of just proxy.foo.com:port (the old syntax is, of course, still supported). The updated patch is available at:

Hi all, I have put together a patch for supporting "Basic" HTTP Proxy Authentication. The patch changes the interpretation of the RSYNC_PROXY environment variable so that the syntax user:pass@proxy.foo:port may be used instead of just proxy.foo:port (the old syntax is of course still supported). The patch has only been tested lightly, but it should(TM) work. The patch (and

on systems that has separate IPv4/v6 socket layer (i.e. IPv4 packet does not get routed to AF_INET6 socket) rsync --daemon would accept IPv6 sessions only. open_socket_in() tries to deal with the situation, but it was not enough. here's the patch. (it is required on all *BSDs to accept both IPv4 and IPv6 connections with --daemon mode) itojun --- ? configure.lineno ? lib/dummy

I am having reports of PCI passthrough problems with SR-IOV, in particular it looks like we are hitting the warning at msi:635 and msi:648 in xen; see the following log: (XEN) [VT-D]iommu.c:1785: VT-d page table not sharing with EPT table xenbus dev backend/vbd/1/5696 error 6 opening device (XEN) PCI add Virtual Function 04:1a.0 (XEN) HVM1: HVM Loader (XEN) HVM1: Detected Xen v4.1.0.rc2.pre (XEN)

Hi, I have installed rsync-2.4.6 version on Linux Redhat 6.2 (Kernel-2.2.14-5.0), after installed I tried to test the rsh and run "rsh remotehost /bin/true > out .dat". But it failed the error message was "Permission denied". I checked the permission all was okay, I forgot the rsh/csh methods and replaced by RSYNC_PROXY. Finally, it failed again. I would like to know that

Hi, all -- Here's a small patch that gives better diagnostics on the daemon side if it fails to start up due to inability to create or bind the socket. Presently, it gives a log entry indicating that no sockets could be bound, but crucially does *not* have the system error message (i.e. errno) from the failed call, making it difficult or impossible to determine the problem. I do have a

Is it possible to rsync through a firewall that requires HTTP basic authentication? The RSYNC_PROXY variable seems to correctly direct the request to go through the HTTP proxy server on the firewall, but there's no way to specify a username/password combo. The error message reported by rsync is "bad response from proxy - HTTP/1.1 401 Authentication required", which is not

Hi all - I've searched long and hard for some docs on configuring a web proxy for rsync. This is probably in part an apache config question so I apologize if this is in the wrong forum. What I would like to do is provide anonymous rsync access to a handful of IPs via a web proxy so I don't have to punch additional holes in my firewall. In other words, I'd like to use rsync over

Hello. I'm having a problem regarding locked users in ldap. We are using 389DS ldap server. We lock our users with nsAccountLock=true. If user successfully logs into dovecot, his credentials gets cached. When this user is locked its credentials still stay in cache. The problem I'm having is that our ldap server returns error code 53 ("Unwilling to perform - Account

Hi all, I am interested at using a web proxy to help speed a transfer across a WAN. Are there any examples of syntax for the RSYNC_PROXY command available? Thanks, Max -- Max Clark <maxc at beast.clarksys.com> My Blog http://www.clarksys.com >> spamtrap: spam@clarksys.com - do NOT ever send email to this address <<

Hello all! I'm trying to syncronize 2 directories on 2 servers (A and B) using 3rd server (C) as proxy server. what i did is: - installed http proxy (tinyproxy) on C and configured it to run on port 873 - default port for rsync protocol. - set the variable RSYNC_PROXY to C-ip:873 using command export RSYNC_PROXY=C-ip:873 - run the rsync command without ssh support. as a result the

Hi All, I'm trying to get rsync to proxy through an apache httpd server to an rsync server. On the proxy, which has a direct connection to the internet, I've stopped the firewall and unset HTTP_PROXY and RSYNC_PROXY. I've configured the httpd to allow proxy requests as follows: <IfModule mod_proxy.c># ProxyRequests On <Proxy *> Order deny,allow Deny from all

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ /users/tconway>man rsync |grep environment Reformatting page. Wait... done environment variable. the environment variable RSYNC_PROXY to a hostname:port pair environment variable RSYNC_PASSWORD to the password you want WARNING: On some systems environment variables are visible RSYNC_RSH

Hi, Does anyone know if it is possible to firewall and/or configure rsync via a web proxy using RSYNC_PROXY to prevent push mode file transfers yet still allow pull mode? I am aware of Matt McCutchen's helpful distinction between the direction of an rsync connection and the direction of file transfer at at http://lists.samba.org/archive/rsync/2006-May/015595.html, but I am after

My computers at my office will no longer be able to connect directly to web sites etc. I will be going through a proxy server. The particular server is running squid on port 3128. I have managed to configure web browsers, ssh, apt, svn and a whole lot of other tools to use the proxy server but I haven't been able to configure rsync. My usual method of updating my copy of the R-devel

ssh-keyscan may, under very specific circumstances, be vulnerable to something akin to a buffer overflow. It's probably impossible to exploit, though, if only because ssh-keyscan is not usually run on very large untrusted input files. ssh-keyscan uses an fgets() wrapper that uses an unsigned int to keep track of the length of a buffer holding the current line. On machines with sufficient

> Hallo, > what is the right way to set a proxy systemwide using centos 7? > I need this for wget and docker. > My first idea was /etc/environment but allthough the proxy is set wget and > docker don? t connect to their target-systems. I have this in /etc/profile.d/proxy-config.sh: -----%<--------------------------------- PROXYHOST="proxy" PROXYPORT="8080"

On 2002-Apr-04 at 02:24:41 -0800, Bardur Arantsson wrote: > I have put together a patch for supporting "Basic" HTTP Proxy > Authentication. The patch changes the interpretatio of the RSYNC_PROXY > environment variable so that the syntax > > user:pass@proxy.foo:port > > may be used instead of just > > proxy.foo:port > > (the old syntax is of course

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to sync a mandrakelinux tree (~120GB) but it bombs out after a while with this error: rsync: connection unexpectedly closed (289336107 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown": Broken pipe rsync error:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Using the following settings: $ export RSYNC_PROXY=www-proxy:3125 $ rsync -av --stats --progress --partial --delete-after --bwlimit=160 rsync://carroll.cac.psu.edu/mandrakelinux/ /export/ftp/mandrakelinux I'll almost certainly get this error at some point during the transfer: rsync: connection unexpectedly closed (320497666 bytes received so