rsyncrypto-devel Mailing List for rsync friendly file encryption (Page 3)
Brought to you by:
thesun
Menu
▾
▴
rsyncrypto-devel — Development discussions, bug reports, and announcements for rsyncrypto
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(7) |
Jun
(5) |
Jul
(12) |
Aug
(29) |
Sep
(6) |
Oct
(5) |
Nov
(18) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(13) |
Feb
(3) |
Mar
|
Apr
(5) |
May
(6) |
Jun
(8) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(23) |
Dec
(2) |
| 2007 |
Jan
(47) |
Feb
(4) |
Mar
(4) |
Apr
|
May
|
Jun
(8) |
Jul
(2) |
Aug
|
Sep
(6) |
Oct
|
Nov
(24) |
Dec
(17) |
| 2008 |
Jan
(4) |
Feb
(22) |
Mar
(25) |
Apr
(19) |
May
(76) |
Jun
(34) |
Jul
(18) |
Aug
(2) |
Sep
|
Oct
(4) |
Nov
|
Dec
(3) |
| 2009 |
Jan
|
Feb
(13) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(9) |
Aug
(7) |
Sep
(2) |
Oct
(3) |
Nov
|
Dec
(4) |
| 2010 |
Jan
|
Feb
(4) |
Mar
|
Apr
(3) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(7) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(1) |
| 2014 |
Jan
|
Feb
|
Mar
(14) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2015 |
Jan
|
Feb
(6) |
Mar
(2) |
Apr
|
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(7) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
|
From: Shachar S. <sh...@sh...> - 2014-03-18 15:08:05
|
On 18/03/14 13:55, Frederico Rodrigues Abraham wrote: > Here is the stack trace: While we're at it, and in addition to the strace output, please try applying the attached patch. It should solve the actual crash, but I suspect rsyncrypto will still fail (just more gracefully). Just cd to the source directory, run "patch -p0 < /tmp/crash.patch", and then run "make" again. Let me know whether it solves the crash. Shachar |
|
From: Shachar S. <sh...@sh...> - 2014-03-18 14:57:48
|
On 18/03/14 13:55, Frederico Rodrigues Abraham wrote: > Here is the stack trace: > > Program received signal SIGSEGV, Segmentation fault. > key::read_key (buffer=buffer@entry=0xffffffffffffffff <Address > 0xffffffffffffffff out of bounds>) at crypt_key.cpp:44 > 44 if( buff->version!=htonl(VERSION_MAGIC_1) ) > (gdb) > (gdb) bt > #0 key::read_key (buffer=buffer@entry=0xffffffffffffffff <Address > 0xffffffffffffffff out of bounds>) at crypt_key.cpp:44 > #1 0x00000000004047f0 in read_header (headfd=...) at crypto.cpp:102 > #2 0x0000000000408a3a in file_decrypt (src_file=0x9357158 > "filesencrypted/files/40AEBACBA5170D57464965CA52861A2F", > dst_file=0x9357238 > "../ugah/files/work/tecgraf/lib/visnew/include/old/sg/strat/render/slrender.h", > key_file=0x93572d8 > "filesencrypted/keys/files/40AEBACBA5170D57464965CA52861A2F", > rsa_key=rsa_key@entry=0x6296a0, stat=stat@entry=0x7fffffffb660) at > file.cpp:445 This makes zero sense. The segmentation fault is due to trying to dereference a pointer pointing to 0xffffffffffffffff (-1), which is what mmap returns when it fails. This, like I said, makes no sense, as in such a case it should have thrown an exception (hmmm...., upon looking at the code again, maybe not...). Can you please run the code with strace and send me (in private) the result? I can see why the error wouldn't be detected on 64 bit, but I still don't understand why mmap would fail to begin with. Thanks, Shachar |
|
From: Frederico R. A. <dev...@gm...> - 2014-03-18 11:56:01
|
Here is the stack trace:
Program received signal SIGSEGV, Segmentation fault.
key::read_key (buffer=buffer@entry=0xffffffffffffffff <Address
0xffffffffffffffff out of bounds>) at crypt_key.cpp:44
44 if( buff->version!=htonl(VERSION_MAGIC_1) )
(gdb)
(gdb) bt
#0 key::read_key (buffer=buffer@entry=0xffffffffffffffff <Address
0xffffffffffffffff out of bounds>) at crypt_key.cpp:44
#1 0x00000000004047f0 in read_header (headfd=...) at crypto.cpp:102
#2 0x0000000000408a3a in file_decrypt (src_file=0x9357158
"filesencrypted/files/40AEBACBA5170D57464965CA52861A2F",
dst_file=0x9357238
"../ugah/files/work/tecgraf/lib/visnew/include/old/sg/strat/render/slrender.h",
key_file=0x93572d8
"filesencrypted/keys/files/40AEBACBA5170D57464965CA52861A2F",
rsa_key=rsa_key@entry=0x6296a0, stat=stat@entry=0x7fffffffb660) at
file.cpp:445
#3 0x0000000000409b80 in recurse_dir_enc (src_dir=src_dir@entry=0x7fffffffc588
"filesencrypted/files", dst_dir=dst_dir@entry=0x7fffffffc59d "..",
key_dir=key_dir@entry=0x7fffffffc5a0 "filesencrypted/keys",
rsa_key=rsa_key@entry=0x6296a0, op=op@entry=0x408990 <file_decrypt(char
const*, char const*, char const*, rsa_st*, stat const*)>,
src_offset=src_offset@entry=15, op_handle_dir=op_handle_dir@entry=false,
opname=opname@entry=0x410569 "Decrypting", dstname=dstname@entry=
0x40c4f0 <filemap::namecat_decrypt(char const*, char const*, unsigned
int)>, keyname=keyname@entry=0x409520 <name_concat(char const*, char
const*, unsigned int)>) at file.cpp:207
#4 0x000000000040a315 in dir_encrypt (src_dir=0x7fffffffc588
"filesencrypted/files", dst_dir=0x7fffffffc59d "..", key_dir=0x7fffffffc5a0
"filesencrypted/keys", rsa_key=rsa_key@entry=0x6296a0,
op=op@entry=0x408990 <file_decrypt(char const*, char const*, char
const*, rsa_st*, stat const*)>, opname=opname@entry=0x410569 "Decrypting",
dstname=dstname@entry=0x40c4f0 <filemap::namecat_decrypt(char const*,
char const*, unsigned int)>, keyname=keyname@entry=0x409520
<name_concat(char const*, char const*, unsigned int)>) at file.cpp:323
#5 0x00000000004030f9 in main (argc=<optimized out>, argv=<optimized out>)
at main.cpp:170
(gdb)
On Sun, Mar 16, 2014 at 11:04 AM, Frederico Rodrigues Abraham <
dev...@gm...> wrote:
> It's saying 'not stripped', cool. Running it.
>
> It's 64 bit intel.
>
> -- Fred
>
>
> On Sun, Mar 16, 2014 at 11:03 AM, Shachar Shemesh <sh...@sh...>wrote:
>
>> On 16/03/14 15:49, Frederico Rodrigues Abraham wrote:
>>
>> ok, ./configure && make worked. but is the executable with debug info? no
>> special flags for 'make' ?
>>
>> "file rsyncrypto"
>>
>> It should say it is "not stripped".
>>
>> Also, what platform is this? Is it 64bit Intel?
>>
>> Shachar
>>
>>
>>
>> On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <sh...@sh...>wrote:
>>
>>> On 16/03/14 15:19, Frederico Rodrigues Abraham wrote:
>>>
>>>
>>> Any ideas?
>>>
>>> Yes. Try to build with the standard "./configure ; make" idiom.
>>> Obviously, the packaging for this has rotted to the point it no longer
>>> compiles :-(
>>>
>>> I'll get around, sometimes, to update the Debian package. The Ubuntu
>>> package, however, is out of my hands. It will get updated on its own or
>>> not. At least on Debian, however, the package complains a lot, but still
>>> compiles.
>>>
>>> I'm not sure whether to tell you to open a bug on the Ubuntu package,
>>> but the manual compile should at least tell us where the problem is.
>>>
>>> Shachar
>>>
>>> Thanks,
>>> -- Fred
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Learn Graph Databases - Download FREE O'Reilly Book
>>> "Graph Databases" is the definitive new guide to graph databases and their
>>> applications. Written by three acclaimed leaders in the field,
>>> this first edition is now available. Download your free book today!http://p.sf.net/sfu/13534_NeoTech
>>>
>>>
>>>
>>> _______________________________________________
>>> Rsyncrypto-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>>>
>>>
>>>
>>
>>
>> --
>> -- Fred
>>
>>
>>
>
>
> --
> -- Fred
>
--
-- Fred
|
|
From: Frederico R. A. <dev...@gm...> - 2014-03-16 14:04:51
|
It's saying 'not stripped', cool. Running it. It's 64 bit intel. -- Fred On Sun, Mar 16, 2014 at 11:03 AM, Shachar Shemesh <sh...@sh...>wrote: > On 16/03/14 15:49, Frederico Rodrigues Abraham wrote: > > ok, ./configure && make worked. but is the executable with debug info? no > special flags for 'make' ? > > "file rsyncrypto" > > It should say it is "not stripped". > > Also, what platform is this? Is it 64bit Intel? > > Shachar > > > > On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <sh...@sh...>wrote: > >> On 16/03/14 15:19, Frederico Rodrigues Abraham wrote: >> >> >> Any ideas? >> >> Yes. Try to build with the standard "./configure ; make" idiom. >> Obviously, the packaging for this has rotted to the point it no longer >> compiles :-( >> >> I'll get around, sometimes, to update the Debian package. The Ubuntu >> package, however, is out of my hands. It will get updated on its own or >> not. At least on Debian, however, the package complains a lot, but still >> compiles. >> >> I'm not sure whether to tell you to open a bug on the Ubuntu package, but >> the manual compile should at least tell us where the problem is. >> >> Shachar >> >> Thanks, >> -- Fred >> >> >> ------------------------------------------------------------------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph databases and their >> applications. Written by three acclaimed leaders in the field, >> this first edition is now available. Download your free book today!http://p.sf.net/sfu/13534_NeoTech >> >> >> >> _______________________________________________ >> Rsyncrypto-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel >> >> >> > > > -- > -- Fred > > > -- -- Fred |
|
From: Shachar S. <sh...@sh...> - 2014-03-16 14:03:46
|
On 16/03/14 15:49, Frederico Rodrigues Abraham wrote: > ok, ./configure && make worked. but is the executable with debug info? > no special flags for 'make' ? "file rsyncrypto" It should say it is "not stripped". Also, what platform is this? Is it 64bit Intel? Shachar > > > On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <sh...@sh... > <mailto:sh...@sh...>> wrote: > > On 16/03/14 15:19, Frederico Rodrigues Abraham wrote: >> >> Any ideas? > Yes. Try to build with the standard "./configure ; make" idiom. > Obviously, the packaging for this has rotted to the point it no > longer compiles :-( > > I'll get around, sometimes, to update the Debian package. The > Ubuntu package, however, is out of my hands. It will get updated > on its own or not. At least on Debian, however, the package > complains a lot, but still compiles. > > I'm not sure whether to tell you to open a bug on the Ubuntu > package, but the manual compile should at least tell us where the > problem is. > > Shachar >> Thanks, >> -- Fred >> >> >> ------------------------------------------------------------------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph databases and their >> applications. Written by three acclaimed leaders in the field, >> this first edition is now available. Download your free book today! >> http://p.sf.net/sfu/13534_NeoTech >> >> >> _______________________________________________ >> Rsyncrypto-devel mailing list >> Rsy...@li... <mailto:Rsy...@li...> >> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel > > > > > -- > -- Fred |
|
From: Frederico R. A. <dev...@gm...> - 2014-03-16 13:49:21
|
ok, ./configure && make worked. but is the executable with debug info? no special flags for 'make' ? On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <sh...@sh...>wrote: > On 16/03/14 15:19, Frederico Rodrigues Abraham wrote: > > > Any ideas? > > Yes. Try to build with the standard "./configure ; make" idiom. Obviously, > the packaging for this has rotted to the point it no longer compiles :-( > > I'll get around, sometimes, to update the Debian package. The Ubuntu > package, however, is out of my hands. It will get updated on its own or > not. At least on Debian, however, the package complains a lot, but still > compiles. > > I'm not sure whether to tell you to open a bug on the Ubuntu package, but > the manual compile should at least tell us where the problem is. > > Shachar > > Thanks, > -- Fred > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today!http://p.sf.net/sfu/13534_NeoTech > > > > _______________________________________________ > Rsyncrypto-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel > > > -- -- Fred |
|
From: Shachar S. <sh...@sh...> - 2014-03-16 13:36:05
|
On 16/03/14 15:19, Frederico Rodrigues Abraham wrote: > > Any ideas? Yes. Try to build with the standard "./configure ; make" idiom. Obviously, the packaging for this has rotted to the point it no longer compiles :-( I'll get around, sometimes, to update the Debian package. The Ubuntu package, however, is out of my hands. It will get updated on its own or not. At least on Debian, however, the package complains a lot, but still compiles. I'm not sure whether to tell you to open a bug on the Ubuntu package, but the manual compile should at least tell us where the problem is. Shachar > Thanks, > -- Fred > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > > > _______________________________________________ > Rsyncrypto-devel mailing list > Rsy...@li... > https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel |
|
From: Frederico R. A. <dev...@gm...> - 2014-03-16 13:19:39
|
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 16-03-2014 00:18, Shachar Shemesh
wrote:<br>
</div>
<blockquote cite="mid:532...@sh..." type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<style type="text/css">body p { margin-bottom: 0.2cm; margin-top: 0pt; } </style>
<div class="moz-cite-prefix">Hello Frederico,<br>
<br>
On 16/03/14 00:48, Frederico Rodrigues Abraham wrote:<br>
</div>
<blockquote cite="mid:532...@gm..." type="cite">
<pre wrap="">Hi all.
My rsyncrypto started crashing ... I'm decrypting directories with
filename encryption.</pre>
</blockquote>
By "started crashing", I'm assuming you mean it did work before.
Can you say what changed?<br>
<br>
Let's start with some background material. What version of
rsyncrypto are you using (run rsyncrypto --version)? Is it the
standard one provided by the distribution? What command line are
you using? (it is okay to fudge the directory names, if those are
sensitive). What is the precise error message?<br>
</blockquote>
<br>
It's the standard provided with the distribution, version 1.12. It
worked before normally, now I'm getting this:<br>
<br>
Decrypting filesencrypted/files/40AEBACBA5170D57464965CA52861A2F<br>
Segmentation fault (core dumped)<br>
<br>
Command line is:<br>
<br>
rsyncrypto -vvvvv -n .ssh/filemap --delete --delete-keys -d -r
filesencrypted/files .. filesencrypted/keys .ssh/backup.key<br>
<br>
(I just added the -vvvvv to try to debug, but no success. Crashes
without it)<br>
<br>
<blockquote cite="mid:532...@sh..." type="cite">
<blockquote cite="mid:532...@gm..." type="cite">
<pre wrap="">
Is it possible for someone to help me investigating this? Without the
need for me to send the actual data?</pre>
</blockquote>
I can certainly try.<br>
<blockquote cite="mid:532...@gm..." type="cite">
<pre wrap="">An executable with debugging information maybe? I'm running on Ubuntu
Linux 13.10.</pre>
</blockquote>
Perform the following tasks to build one (assuming you are running
the distribution's binary):<br>
create a clean directory and cd to it<br>
sudo apt-get build-dep rsyncrypto<br>
apt-get source rsyncrypto<br>
cd rsyncrypto-<version><br>
dpkg-buildpackage<br>
<br>
your work directory should have a non-stripped (i.e. - with debug
info) version of the file. Use it. Make sure to run "ulimit -c
unlimited" first. After crash, a file called "core" should be
created. Run "gdb <path to>/rsyncrypto core", type "bt", and
paste the output here. This will provide a backtrace of the point
of the crash.<br>
</blockquote>
<br>
I got an error. After the commands:<br>
<br>
130 9:38 mkdir rsyncryptodebug<br>
131 9:38 cd rsyncryptodebug<br>
132 9:38 sudo apt-get build-dep rsyncrypto<br>
133 9:39 apt-get source rsyncrypto<br>
134 9:40 cd rsyncrypto-1.12/<br>
135 9:40 dpkg-buildpackage<br>
<br>
[bacon:/local2/users/fabraham/pessoal/backup/rsyncryptodebug/rsyncrypto-1.12]
dpkg-buildpackage<br>
dpkg-buildpackage: source package rsyncrypto<br>
dpkg-buildpackage: source version 1.12-1build1<br>
dpkg-buildpackage: source changed by Colin Watson <a
class="moz-txt-link-rfc2396E" href="mailto:cjw...@ub..."><cjw...@ub...></a><br>
dpkg-buildpackage: host architecture amd64<br>
dpkg-source --before-build rsyncrypto-1.12<br>
fakeroot debian/rules clean<br>
dh_testdir<br>
dh_testroot<br>
rm -f build-stamp<br>
[ ! -f Makefile ] || /usr/bin/make distclean<br>
dh_clean<br>
dh_clean: Compatibility levels before 5 are deprecated (level 4 in
use)<br>
dpkg-source -b rsyncrypto-1.12<br>
dpkg-source: warning: no source format specified in
debian/source/format, see dpkg-source(1)<br>
dpkg-source: info: using source format `1.0'<br>
dpkg-source: info: building rsyncrypto using existing
rsyncrypto_1.12.orig.tar.gz<br>
dpkg-source: info: building rsyncrypto in
rsyncrypto_1.12-1build1.diff.gz<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto_1.12-1build1.diff.gz: binary file
contents changed<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto_1.12.orig.tar.gz: binary file contents
changed<br>
dpkg-source: warning: file
rsyncrypto-1.12/rsyncrypto-1.12/COPYING.rtf has no final newline
(either original or modified version)<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/install-sh' will not be represented in diff<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/depcomp' will not be represented in diff<br>
dpkg-source: warning: file
rsyncrypto-1.12/rsyncrypto-1.12/INSTALL.win has no final newline
(either original or modified version)<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/bootstrap' will not be represented in diff<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/configure' will not be represented in diff<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/missing' will not be represented in diff<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/debian/rules' will not be represented in diff<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg1.key: binary file contents
changed<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg1.enc: binary file contents
changed<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg2.key: binary file contents
changed<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg3: binary file contents
changed<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg1: binary file contents
changed<br>
dpkg-source: warning: newly created empty file
'rsyncrypto-1.12/tests/reg2.rot' will not be represented in diff<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg3.enc: binary file contents
changed<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/tests/testcrypt' will not be represented in diff<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/tests/nullgzip' will not be represented in diff<br>
dpkg-source: warning: newly created empty file
'rsyncrypto-1.12/tests/reg1.rot' will not be represented in diff<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg2.enc: binary file contents
changed<br>
dpkg-source: warning: executable mode 0755 of
'rsyncrypto-1.12/tests/regtest' will not be represented in diff<br>
dpkg-source: warning: file
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg2 has no final newline
(either original or modified version)<br>
dpkg-source: error: cannot represent change to
rsyncrypto-1.12/rsyncrypto-1.12/tests/reg3.key: binary file contents
changed<br>
dpkg-source: warning: file
rsyncrypto-1.12/rsyncrypto-1.12/win32/nullgzip.cpp has no final
newline (either original or modified version)<br>
dpkg-source: warning: file
rsyncrypto-1.12/rsyncrypto-1.12/win32/types.h has no final newline
(either original or modified version)<br>
dpkg-source: warning: file
rsyncrypto-1.12/rsyncrypto-1.12/win32/win32redir.h has no final
newline (either original or modified version)<br>
dpkg-source: warning: the diff modifies the following upstream
files:<br>
config.guess<br>
config.sub<br>
rsyncrypto-1.12/AUTHORS<br>
rsyncrypto-1.12/COPYING<br>
rsyncrypto-1.12/COPYING.rtf<br>
rsyncrypto-1.12/ChangeLog<br>
rsyncrypto-1.12/INSTALL<br>
rsyncrypto-1.12/INSTALL.win<br>
rsyncrypto-1.12/Makefile.am<br>
rsyncrypto-1.12/Makefile.in<br>
rsyncrypto-1.12/NEWS<br>
rsyncrypto-1.12/README<br>
rsyncrypto-1.12/aclocal.m4<br>
rsyncrypto-1.12/aes_crypt.cpp<br>
rsyncrypto-1.12/aes_crypt.h<br>
rsyncrypto-1.12/autoarray.h<br>
rsyncrypto-1.12/autodir.h<br>
rsyncrypto-1.12/autofd.h<br>
rsyncrypto-1.12/autommap.h<br>
rsyncrypto-1.12/autopipe.h<br>
rsyncrypto-1.12/blocksizes.cpp<br>
rsyncrypto-1.12/bootstrap<br>
rsyncrypto-1.12/bufferfd.cpp<br>
rsyncrypto-1.12/bufferfd.h<br>
rsyncrypto-1.12/config.guess<br>
rsyncrypto-1.12/config.h.in<br>
rsyncrypto-1.12/config.sub<br>
rsyncrypto-1.12/configure<br>
rsyncrypto-1.12/configure.ac<br>
rsyncrypto-1.12/contrib/argtable2.vcproj<br>
rsyncrypto-1.12/contrib/gzip-rsyncable.diff<br>
rsyncrypto-1.12/crypt_key.cpp<br>
rsyncrypto-1.12/crypt_key.h<br>
rsyncrypto-1.12/crypto.cpp<br>
rsyncrypto-1.12/crypto.h<br>
rsyncrypto-1.12/debian/README.Debian<br>
rsyncrypto-1.12/debian/changelog<br>
rsyncrypto-1.12/debian/compat<br>
rsyncrypto-1.12/debian/control<br>
rsyncrypto-1.12/debian/copyright<br>
rsyncrypto-1.12/debian/dirs<br>
rsyncrypto-1.12/debian/docs<br>
rsyncrypto-1.12/debian/rsyncrypto.examples<br>
rsyncrypto-1.12/debian/rules<br>
rsyncrypto-1.12/debian/watch<br>
rsyncrypto-1.12/depcomp<br>
rsyncrypto-1.12/docs/filelist.txt<br>
rsyncrypto-1.12/docs/rsyncrypto.html<br>
rsyncrypto-1.12/docs/rsyncrypto_recover.html<br>
rsyncrypto-1.12/file.cpp<br>
rsyncrypto-1.12/file.h<br>
rsyncrypto-1.12/filemap.cpp<br>
rsyncrypto-1.12/filemap.h<br>
rsyncrypto-1.12/install-sh<br>
rsyncrypto-1.12/main.cpp<br>
rsyncrypto-1.12/missing<br>
rsyncrypto-1.12/precomp.h<br>
rsyncrypto-1.12/process.cpp<br>
rsyncrypto-1.12/process.h<br>
rsyncrypto-1.12/random.h<br>
rsyncrypto-1.12/rcserror.h<br>
rsyncrypto-1.12/recover.cpp<br>
rsyncrypto-1.12/redir.cpp<br>
rsyncrypto-1.12/redir.h<br>
rsyncrypto-1.12/release.checklist<br>
rsyncrypto-1.12/rsyncrypto.h<br>
rsyncrypto-1.12/rsyncrypto.man<br>
rsyncrypto-1.12/rsyncrypto.sln<br>
rsyncrypto-1.12/rsyncrypto.vcproj<br>
rsyncrypto-1.12/rsyncrypto_recover.man<br>
rsyncrypto-1.12/rsyncrypto_recover.vcproj<br>
rsyncrypto-1.12/tests/README<br>
rsyncrypto-1.12/tests/cert.crt<br>
rsyncrypto-1.12/tests/cert.key<br>
rsyncrypto-1.12/tests/nullgzip<br>
rsyncrypto-1.12/tests/reg2<br>
rsyncrypto-1.12/tests/reg3.rot<br>
rsyncrypto-1.12/tests/regtest<br>
rsyncrypto-1.12/tests/regtestw32<br>
rsyncrypto-1.12/tests/testcrypt<br>
rsyncrypto-1.12/win32/Setup.vdproj<br>
rsyncrypto-1.12/win32/autodir.h<br>
rsyncrypto-1.12/win32/autofd.h<br>
rsyncrypto-1.12/win32/autohandle.h<br>
rsyncrypto-1.12/win32/autommap.h<br>
rsyncrypto-1.12/win32/autopipe.h<br>
rsyncrypto-1.12/win32/config.h<br>
rsyncrypto-1.12/win32/nullgzip.cpp<br>
rsyncrypto-1.12/win32/nullgzip.vcproj<br>
rsyncrypto-1.12/win32/process.cpp<br>
rsyncrypto-1.12/win32/process.h<br>
rsyncrypto-1.12/win32/redir.cpp<br>
rsyncrypto-1.12/win32/resource.h<br>
rsyncrypto-1.12/win32/rsyncrypto.rc<br>
rsyncrypto-1.12/win32/stdafx.cpp<br>
rsyncrypto-1.12/win32/types.h<br>
rsyncrypto-1.12/win32/win32glue.cpp<br>
rsyncrypto-1.12/win32/win32redir.h<br>
rsyncrypto_1.12-1build1.dsc<br>
dpkg-source: info: use the '3.0 (quilt)' format to have separate and
documented changes to upstream files, see dpkg-source(1)<br>
dpkg-source: unrepresentable changes to source<br>
dpkg-buildpackage: error: dpkg-source -b rsyncrypto-1.12 gave error
exit status 1<br>
<br>
Any ideas?<br>
Thanks,<br>
-- Fred<br>
</body>
</html>
|
|
From: Shachar S. <sh...@sh...> - 2014-03-16 03:35:39
|
Hello Frederico, On 16/03/14 00:48, Frederico Rodrigues Abraham wrote: > Hi all. > My rsyncrypto started crashing ... I'm decrypting directories with > filename encryption. By "started crashing", I'm assuming you mean it did work before. Can you say what changed? Let's start with some background material. What version of rsyncrypto are you using (run rsyncrypto --version)? Is it the standard one provided by the distribution? What command line are you using? (it is okay to fudge the directory names, if those are sensitive). What is the precise error message? > > Is it possible for someone to help me investigating this? Without the > need for me to send the actual data? I can certainly try. > An executable with debugging information maybe? I'm running on Ubuntu > Linux 13.10. Perform the following tasks to build one (assuming you are running the distribution's binary): create a clean directory and cd to it sudo apt-get build-dep rsyncrypto apt-get source rsyncrypto cd rsyncrypto-<version> dpkg-buildpackage your work directory should have a non-stripped (i.e. - with debug info) version of the file. Use it. Make sure to run "ulimit -c unlimited" first. After crash, a file called "core" should be created. Run "gdb <path to>/rsyncrypto core", type "bt", and paste the output here. This will provide a backtrace of the point of the crash. Hopefully, I can try and help you more after that. Shachar |
|
From: Frederico R. A. <dev...@gm...> - 2014-03-15 22:48:23
|
Hi all. My rsyncrypto started crashing ... I'm decrypting directories with filename encryption. Is it possible for someone to help me investigating this? Without the need for me to send the actual data? An executable with debugging information maybe? I'm running on Ubuntu Linux 13.10. Thanks, -- Fred |
|
From: Frederico R. A. <dev...@gm...> - 2012-12-17 10:14:19
|
"Filename translation not found(68110080386DA2B864AE4D5D74D9F90B): Success" hello all. i am using file name encryption and keep getting this message. when comparing the original data and decrypted data, some files also appear only among the decrypted data (files i have removed from the original data). first question: is this because rsyncrypto was able to decrypt a file name even when it was not on the map file? second question: the file (and key) exist in the encrypted directory but not on the contents of the file map. how come? the command i'm using is: rsyncrypto --modify-window 300 -v --delete --delete-keys -c -n /home/ugah/.ssh/filemap -r /home/ugah/files /home/ugah/filesencrypted/files /home/ugah/filesencrypted/keys /home/ugah/.ssh/backup.crt thank you, -- Fred |
|
From: Shachar S. <sh...@sh...> - 2012-11-29 18:57:51
|
On 11/29/2012 06:47 PM, chr...@gm... wrote: > > Hi Shachar, > > > > thanks for the quick response. You are correct, I can work with that, > it's just that I'm running it from a threaded Delphi application that > poles the command output pipe, so with and it not passing anything > back I'm not detecting the exit. > > > > I think I'll have to improve my monitoring of the pipe. > That is the preferred solution. Another is to detect when rsyncrypto exits (the pipe is closed), and then, if you do not see any errors, to assume everything is okay. I will repeat, for the sake of emphasis, that the first option is the recommended one. Good luck, Shachar -- Shachar Shemesh |
|
From: Shachar S. <sh...@sh...> - 2012-11-28 20:06:53
|
On 11/28/2012 09:12 PM, Chris Whatling wrote: > Hi, I'm trying to run Rsyncrypto followed by rsync in a sequence to encrypt > and then sync a number of files and folders. > > The problem I am having is that Rsyncrypto does not seem to output any message > or other text upon successful completion. It outputs 'Encrypting ..file .. etc > for each file, but nothing to indicate when it has finished the last one. > > I have tried increasing the verbosity with -v -v etc. which produces > additional output but nothing that indicates when it's done. > > Maybe I'm missing somthing obvious? Hi Chris, I'm just throwing ideas around, here, but isn't the fact it exits with return code zero indication enough that it completed successfully? Shachar -- Shachar Shemesh |
|
From: Chris W. <chr...@gm...> - 2012-11-28 19:20:09
|
Hi, I'm trying to run Rsyncrypto followed by rsync in a sequence to encrypt and then sync a number of files and folders. The problem I am having is that Rsyncrypto does not seem to output any message or other text upon successful completion. It outputs 'Encrypting ..file .. etc for each file, but nothing to indicate when it has finished the last one. I have tried increasing the verbosity with -v -v etc. which produces additional output but nothing that indicates when it's done. Maybe I'm missing somthing obvious? Any suggestions would be appreciated. Thank. Regards Chris. |
|
From: Shlomi F. <sh...@sh...> - 2012-06-23 17:56:13
|
Hi Shachar, On Thu, 21 Jun 2012 20:48:58 +0300 Shachar Shemesh <sh...@sh...> wrote: > On 06/21/2012 06:06 PM, Shlomi Fish wrote: > >> But despair not. You can achieve the equivalent level of security by > >> encrypting your private key with a password, and storing it using the > >> same provider you store your actual data. At this point in time > >> rsyncrypto does not support decrypting from password protected RSA keys, > >> but such support can be, fairly easily, added. Otherwise, in case of > >> catastrophe, you can simply pull your encrypted key and decrypt is locally. > >> > > Thanks! I think that is also what Harold suggested. > Same end result, give or take. Different mechanism. > > RSA keys can be encrypted via a fairly standard fashion that has nothing > to do with pgp or gpg. Openssl knows how to open such encrypted keys, > and so will a future version of rsyncrypto. I see - thanks for the clarification. > > > > BTW, do you think it would be possible to write an --rsyncable patch for xz > > instead of gzip (see http://tukaani.org/xz/ ; http://en.wikipedia.org/wiki/Xz ) > I think you meant LZMA. Well, LZMA is the general algorithm while xz is my favourite implementation of it. > After spending a couple of minutes reading on > it, my gut feeling is that turning it rsyncable in any meaningful way > will greatly hurt the compression ratios you're used to seeing from it, > negating the reason you wanted to use it to begin with. It achieves > better compression ratios by having a very big lookback buffer (encoded > as a dictionary), which is the exact opposite of rsyncability. I see, OK. Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ Chuck Norris/etc. Facts - http://www.shlomifish.org/humour/bits/facts/ Writing a BitKeeper replacement is probably easier at this point than getting its license changed. — Matt Mackall (who ended up writing a BitKeeper replacement) Please reply to list if it's a mailing list post - http://shlom.in/reply . |
|
From: Shachar S. <sh...@sh...> - 2012-06-21 17:49:08
|
On 06/21/2012 06:06 PM, Shlomi Fish wrote: >> But despair not. You can achieve the equivalent level of security by >> encrypting your private key with a password, and storing it using the >> same provider you store your actual data. At this point in time >> rsyncrypto does not support decrypting from password protected RSA keys, >> but such support can be, fairly easily, added. Otherwise, in case of >> catastrophe, you can simply pull your encrypted key and decrypt is locally. >> > Thanks! I think that is also what Harold suggested. Same end result, give or take. Different mechanism. RSA keys can be encrypted via a fairly standard fashion that has nothing to do with pgp or gpg. Openssl knows how to open such encrypted keys, and so will a future version of rsyncrypto. > > BTW, do you think it would be possible to write an --rsyncable patch for xz > instead of gzip (see http://tukaani.org/xz/ ; http://en.wikipedia.org/wiki/Xz ) I think you meant LZMA. After spending a couple of minutes reading on it, my gut feeling is that turning it rsyncable in any meaningful way will greatly hurt the compression ratios you're used to seeing from it, negating the reason you wanted to use it to begin with. It achieves better compression ratios by having a very big lookback buffer (encoded as a dictionary), which is the exact opposite of rsyncability. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com |
|
From: Shlomi F. <sh...@sh...> - 2012-06-21 15:34:43
|
Hi Shachar, sorry for the late response. On Fri, 15 Jun 2012 17:01:51 +0300 Shachar Shemesh <sh...@sh...> wrote: > On 06/15/2012 12:48 PM, Shlomi Fish wrote: > > Hi all, > > > > thanks for rsyncrypto. > you are welcome. > > > > I've become interested in it because I recently decided to use remote > > backups on http://rsync.net/ and want to keep my backups' secure. The first > > thing I wanted to note is that as of the latest release of rsyncrypto (1.12), > > the man page reads "fro stdin" instead of "from stdin". I saw this is fixed in > > the Subversion repository, so isn’t it time for a new release? > The subversion contains some fairly major changes which I have not had > the time to complete. I will release when they are ready. Hopefully, > I'll have more time for rsyncrypto soon. I see, thanks for the heads’ up. > > Otherwise I wanted to ask a question: what I want to do is have the encoded > > data encrypted by a password, which I enter for encrypting and for > > decrypting, so that I can still unpack/decode it if I just have access to the > > encoded data. How can this be achieved while still making the encoded data > > rsync-friendly? Does rsyncrypto support something like that? Should I look for > > something else? > Rsyncrypto uses a public/private key as the master encryption key, with > each file being encrypted using a symmetrical (AES) key. While it is > possible to produce an (insecure) symmetrical key from a password, no > such method exists for public keys. As such, no, rsyncrypto does not > support this mode of use. OK. > > But despair not. You can achieve the equivalent level of security by > encrypting your private key with a password, and storing it using the > same provider you store your actual data. At this point in time > rsyncrypto does not support decrypting from password protected RSA keys, > but such support can be, fairly easily, added. Otherwise, in case of > catastrophe, you can simply pull your encrypted key and decrypt is locally. > Thanks! I think that is also what Harold suggested. BTW, do you think it would be possible to write an --rsyncable patch for xz instead of gzip (see http://tukaani.org/xz/ ; http://en.wikipedia.org/wiki/Xz ) in order to achieve better compression (and as a result faster uploads/downloads) and to adapt rsyncrypto to it? Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ http://www.shlomifish.org/humour/ways_to_do_it.html We don’t know his cellphone number, and even if we did, we would tell you that we didn’t know it. Please reply to list if it's a mailing list post - http://shlom.in/reply . |
|
From: Shlomi F. <sh...@sh...> - 2012-06-21 15:31:18
|
Hi Harold, sorry for the late response. On Fri, 15 Jun 2012 08:52:56 -0500 hg...@an... wrote: > From: Shlomi Fish <sh...@sh...> > Date: Fri, 15 Jun 2012 12:48:08 +0300 > > [...] > > I've become interested in it because I recently decided to > use remote backups on http://rsync.net/ and want to keep > my backups' secure.... > > I do exactly this and it came in real handy when the 2011 Joplin > tornado trashed my apartment, one of my systems next to my balcony > window and my backup disks but fortunately not my main systems: > > http://www.ancell-ent.com/1715_Rex_Ave_127B_Joplin/images/ > Sorry to hear about that. > Otherwise I wanted to ask a question: what I want to do is > have the encoded data encrypted by a password, which I > enter for encrypting and for decrypting, so that I can > still unpack/decode it if I just have access to the > encoded data. How can this be achieved while still making > the encoded data rsync-friendly? Does rsyncrypto support > something like that? Should I look for something else? > > Well, while I didn't need it since the private key was on my > main systems, my last ditch retrival contingency was simply > a printout of the private key which I put copies of elsewhere. > As an alternative, you could encrypt that with something like > gpg, e.g.: > > gpg -c --symmetric --cipher-algo AES --passphrase "supply your own" the-key-file > > And then store that on rsync.net. > Ah, interesting - I misunderstood you at first and thought you suggested to encrypt the entire tarball using this method (which would beat the point because the GPG encryption is not rsync-friendly). Thanks for the tip. Regards, Shlomi Fish > - Harold > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rsyncrypto-devel mailing list > Rsy...@li... > https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ List of Portability Libraries - http://shlom.in/port-libs There are no deletionists. Only Wikipedia articles which Chuck Norris allows to live. (By: joeyadams) Please reply to list if it's a mailing list post - http://shlom.in/reply . |
|
From: Shachar S. <sh...@sh...> - 2012-06-15 14:18:49
|
On 06/15/2012 12:48 PM, Shlomi Fish wrote: > Hi all, > > thanks for rsyncrypto. you are welcome. > > I've become interested in it because I recently decided to use remote > backups on http://rsync.net/ and want to keep my backups' secure. The first > thing I wanted to note is that as of the latest release of rsyncrypto (1.12), > the man page reads "fro stdin" instead of "from stdin". I saw this is fixed in > the Subversion repository, so isn’t it time for a new release? The subversion contains some fairly major changes which I have not had the time to complete. I will release when they are ready. Hopefully, I'll have more time for rsyncrypto soon. > Otherwise I wanted to ask a question: what I want to do is have the encoded > data encrypted by a password, which I enter for encrypting and for > decrypting, so that I can still unpack/decode it if I just have access to the > encoded data. How can this be achieved while still making the encoded data > rsync-friendly? Does rsyncrypto support something like that? Should I look for > something else? Rsyncrypto uses a public/private key as the master encryption key, with each file being encrypted using a symmetrical (AES) key. While it is possible to produce an (insecure) symmetrical key from a password, no such method exists for public keys. As such, no, rsyncrypto does not support this mode of use. But despair not. You can achieve the equivalent level of security by encrypting your private key with a password, and storing it using the same provider you store your actual data. At this point in time rsyncrypto does not support decrypting from password protected RSA keys, but such support can be, fairly easily, added. Otherwise, in case of catastrophe, you can simply pull your encrypted key and decrypt is locally. Hope this helps, Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com |
|
From: <hg...@an...> - 2012-06-15 14:11:31
|
From: Shlomi Fish <sh...@sh...> Date: Fri, 15 Jun 2012 12:48:08 +0300 [...] I've become interested in it because I recently decided to use remote backups on http://rsync.net/ and want to keep my backups' secure.... I do exactly this and it came in real handy when the 2011 Joplin tornado trashed my apartment, one of my systems next to my balcony window and my backup disks but fortunately not my main systems: http://www.ancell-ent.com/1715_Rex_Ave_127B_Joplin/images/ Otherwise I wanted to ask a question: what I want to do is have the encoded data encrypted by a password, which I enter for encrypting and for decrypting, so that I can still unpack/decode it if I just have access to the encoded data. How can this be achieved while still making the encoded data rsync-friendly? Does rsyncrypto support something like that? Should I look for something else? Well, while I didn't need it since the private key was on my main systems, my last ditch retrival contingency was simply a printout of the private key which I put copies of elsewhere. As an alternative, you could encrypt that with something like gpg, e.g.: gpg -c --symmetric --cipher-algo AES --passphrase "supply your own" the-key-file And then store that on rsync.net. - Harold |
|
From: Shlomi F. <sh...@sh...> - 2012-06-15 10:26:15
|
Hi all, thanks for rsyncrypto. I've become interested in it because I recently decided to use remote backups on http://rsync.net/ and want to keep my backups' secure. The first thing I wanted to note is that as of the latest release of rsyncrypto (1.12), the man page reads "fro stdin" instead of "from stdin". I saw this is fixed in the Subversion repository, so isn’t it time for a new release? Otherwise I wanted to ask a question: what I want to do is have the encoded data encrypted by a password, which I enter for encrypting and for decrypting, so that I can still unpack/decode it if I just have access to the encoded data. How can this be achieved while still making the encoded data rsync-friendly? Does rsyncrypto support something like that? Should I look for something else? Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ List of Portability Libraries - http://shlom.in/port-libs <rindolf> I am not solvable. I am Turing hard. Please reply to list if it's a mailing list post - http://shlom.in/reply . |
|
From: Shachar S. <sh...@sh...> - 2011-07-15 07:21:27
|
On 15/07/11 08:36, 阮巧海 wrote: > Hi: > > There are two decision functions. > The one in gzip triggers if the sum of the past 4096 bytes divides > (plain text) by 4096 with zero remainder. > The another one in rsyncrypto triggers if the sum of the past 256 > bytes divides (compressed plain text) by 8192 with zero remainder. Of > course, the block size must be 8192 bytes at least. > > But the homepage explains that finally the performance for the > decision function is that it triggers if the sum of the past 8196 > bytes divides by 4096 with zero remainder. > Can you tell me how to work out the final decision function? > Or you get the final decision function first, and then extend it to > gzip and rsyncrypto? No (not yet?) At its current implementation, rsyncrypto encapsulates two passes over the data. The first is the compression stage, and it takes place using the stock installed gzip with the --rsyncable flag. At this point, whatever decision function gzip implements gets used over the plain text to reset the compression history. The second stage is the encryption. At this stage, the compressed data is used in order to trigger the decision function inside rsyncrypto. Rsyncrypto has flags to tweek the precise decision function (the roll-win, roll-min and roll-sensitivity parameters), but the defaults, indeed, are not identical to those used by gzip. There are some future plans to not use the gzip executable, but rather to use zlib, and only have one decision function reset both encryption and compression parameters. At this point in time, I cannot tell you when, or even if, they will ever take place. Shachar > > Thanks. -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com |
|
From: 阮巧海 <rq...@gm...> - 2011-07-15 05:36:18
|
Hi: There are two decision functions. The one in gzip triggers if the sum of the past 4096 bytes divides (plain text) by 4096 with zero remainder. The another one in rsyncrypto triggers if the sum of the past 256 bytes divides (compressed plain text) by 8192 with zero remainder. Of course, the block size must be 8192 bytes at least. But the homepage explains that finally the performance for the decision function is that it triggers if the sum of the past 8196 bytes divides by 4096 with zero remainder. Can you tell me how to work out the final decision function? Or you get the final decision function first, and then extend it to gzip and rsyncrypto? Thanks. |
|
From: Shachar S. <sh...@sh...> - 2011-06-28 07:46:02
|
On 28/06/11 02:33, Eric W. Anderson wrote: > Hello, > > I've been using rsyncrypto to enable remote backups via rsnapshot without > needing remote-root ssh access. I wrote up my configuration in response to a > question on the rsnapshot mailing list, so I thought I'd share it here too. If > anyone wants to take a look or offer suggestions, it's here: > https://github.com/ewa/rsyncrypto-rsnapshot-config > > Thanks, > Eric Hello Eric, Thank you for sharing this. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com |
|
From: Eric W. A. <and...@ec...> - 2011-06-27 23:33:56
|
Hello, I've been using rsyncrypto to enable remote backups via rsnapshot without needing remote-root ssh access. I wrote up my configuration in response to a question on the rsnapshot mailing list, so I thought I'd share it here too. If anyone wants to take a look or offer suggestions, it's here: https://github.com/ewa/rsyncrypto-rsnapshot-config Thanks, Eric -- Eric W. Anderson Electrical and Computer Engineering and...@ec... Carnegie Mellon University phone: +1-412-268-1908 Hamerschlag A311 PGP key fingerprint: D3C5 D6FF EDED 9F1F C36D 53A3 74B7 53A6 3C74 5F12 |
7 messages has been excluded from this view by a project administrator.
