-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You are missing the point of the checksum. It is a verification that
the file was assembled on the target system correctly. The only
post-transfer checksum that would make any sense locally would be to
make sure that the disk stored the file correctl
Hello. Please see http://unix.stackexchange.com/a/66702. I would like
to have confirmation whether or not rsync verifies the transferred
files' integrity at the target location by checksumming as advertised
in the manpage:
"""Note that rsync always verifies that each transferred file was
correctly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, that would work but as you say it would only work for key
authentication and you would have to control the users'
authorized_keys files.
Also, that isn't the one that would require %h or %u. The alternative
would be something like:
command="/pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First off, this isn't "restricted shell". Second, the user's shell
can also match the forced command so that no shell (especially bash)
is involved.
On 12/03/2014 03:09 PM, devz...@web.de wrote:
>> The benefit of rsync over ssh secured by rrsync is t
On 12/03/2014 01:37:58 PM, Kevin Korb wrote:
> As far as a backup provider goes I wouldn't expect them to use rsync
> over SSL unless that were built into rsync in the future (and has
> been
> around long enough that most users would have it).
>
> I would expect them to either use rsync over ssh
from a security perspective this is bad. think of a backup provider who wants
to make rsyncd modules available to the end users so they can push backups to
the server. do you think that such server is secure if all users are allowed to
open up an ssh shell to secure their rsync transfer ?
ok, y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You mean like grsync?
On 12/03/2014 01:11 PM, Dave Taht wrote:
> On Wed, Dec 3, 2014 at 9:40 AM, Tomasz Chmielewski
> wrote:
>> rsync in daemon mode is very powerful, yet it comes with one big
>> disadvantage: data is sent in plain.
>>
>> The worka
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You can run rsyncd over ssh as well. Either with -e ssh host::module
or you can use ssh's -L to tunnel the rsyncd port. The difference is
which user ends up running the rsyncd.
On 12/03/2014 12:40 PM, Tomasz Chmielewski wrote:
> rsync in daemon mode
On Wed, Dec 3, 2014 at 9:40 AM, Tomasz Chmielewski wrote:
> rsync in daemon mode is very powerful, yet it comes with one big
> disadvantage: data is sent in plain.
>
> The workarounds are not really satisfying:
>
>
> - use VPN - one needs to set up an extra service, not always possible
>
> - use s
rsync in daemon mode is very powerful, yet it comes with one big
disadvantage: data is sent in plain.
The workarounds are not really satisfying:
- use VPN - one needs to set up an extra service, not always possible
- use stunnel - as above
- use SSH - is not as powerful as in daemon mode (i.
On Wed 03 Dec 2014, yhu2 wrote:
> On 11/28/2014 09:41 AM, yhu2 wrote:
> >
> >thanks your reply, could you please send off official fix?
>
> or could you please tell me which release will include this patch. any
> comments would be appreciated!
The git repository is browseable, the patch for this
On 11/28/2014 09:41 AM, yhu2 wrote:
thanks your reply, could you please send off official fix?
or could you please tell me which release will include this patch. any
comments would be appreciated!
Yadi
On 11/28/2014 04:05 AM, Wayne Davison wrote:
On Sun, Nov 16, 2014 at 10:44 PM, yhu2
12 matches
Mail list logo