Displaying 10 results from an estimated 10 matches for "tromer".
Did you mean:
romer
2016 Mar 05
1
is tinc vulnerable to this?
Hello, did you read this paper?
ECDSA Key Extraction from Mobile Devices via Nonintrusive Physical Side
Channels
https://www.cs.tau.ac.il/~tromer/mobilesc/
2006 Feb 22
2
[librsync-users] MD4 second-preimage attack
On Tue, 2006-02-21 at 14:58 -0800, rsync2eran@tromer.org wrote:
> A year ago we discussed the strength of the MD4 hash used by rsync and
> librsync, and one of the points mentioned was that only collision
> attacks are known on MD4.
Could you please forward this into the bug tracker so it's not lost?
--
Martin
-------------- next pa...
2005 Jul 28
2
Filename enocings
Hello everyone,
I have run into the same issue which the fname-convert patch solves:
http://rsync.samba.org/ftp/unpacked/rsync/patches/fname-convert.diff
i.e. rsyncing between and latin 1 and utf-8 locales.
First I'd really like to thank Eran Tromer for providing the patch as
this fixes my immediate issue! I've attached an updated version which
applies to the rsync-2.6.5 release and includes updates to proto.h.
I must admit, I would have been fully pleased with a libiconv solution
that merely interprets the file names in the character se...
2004 Mar 10
1
MD4 checksum_seed
Hi,
The following lines in compat.c are rather imprudent:
if (read_batch || write_batch)
checksum_seed = 32761;
else
checksum_seed = time(NULL);
write_int(f_out,checksum_seed);
Setting checksum_seed to a constant in batch mode means block collisions
are reproducible and predictable. Thus, some files will be permanently
"unlucky" in batch mode and will
2004 May 15
1
Fwd: Re: setting checksum_seed
...://lists.samba.org/archive/rsync/2004-February/008616.html
Earlier, I submitted a patch (against 2.5.6pre1 in Jan 2003)
for --checksum-seed=NUM:
http://lists.samba.org/archive/rsync/2003-January/004845.html
Since I posted both of these patches, there was an interesting thread
started by Eran Tromer about potential block checksum collisions that
could be exploited by someone to trigger first-pass failures. See:
http://lists.samba.org/archive/rsync/2004-March/008821.html
The consequence is just a performance penalty, since with very
high probability the whole-file checksum fails, triggeri...
2004 May 29
1
[patch] Filename conversion
....6.2/fnameconv.c rsync-2.6.2-fnameconv.clean/fnameconv.c
--- rsync-2.6.2/fnameconv.c 1970-01-01 02:00:00.000000000 +0200
+++ rsync-2.6.2-fnameconv.clean/fnameconv.c 2004-05-29 21:17:09.000000000 +0300
@@ -0,0 +1,224 @@
+/* -*- c-file-style: "linux" -*-
+ *
+ * Copyright (C) 2004 by Eran Tromer
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed i...
2002 Aug 05
5
[patch] read-devices
...tics straight.
For instance, the token sending functions now return the number of data
bytes they read.
A few things I wasn't sure about are marked by "#ET#".
I hope it would be possible to incorporate this patch into rsync, after
proper review and testing.
Regards,
Eran Tromer
-------------- next part --------------
diff -r -u4 rsync-2.5.5/checksum.c rsync-patched/checksum.c
--- rsync-2.5.5/checksum.c Tue Oct 26 01:04:09 1999
+++ rsync-patched/checksum.c Mon Aug 5 10:05:15 2002
@@ -24,8 +24,9 @@
#define CSUM_CHUNK 64
int checksum_seed = 0;
extern int remote_version...
2019 Apr 11
4
Understanding Problem with rsa min key length 1024
Hello,
Sometime ago min rsa key length was increased to 1024 bit and i have a
little understanding problem with this.
I hope somebody with some crypto-experience can enlighten me. To make
that clear, that is not about allowing lower keys in general.
Personally i would tend to use even longer keys(2048bit+).
However Due nature of RSA-algorithm in case of 1024bit this might result
in a key
2004 Jul 12
2
[PATCH] Batch-mode rewrite
Wayne,
Please consider the attached patch. This applies to the current
CVS, and is independant of patches/local-batch.diff. As a matter of
fact, I'm sure it would conflict heavily with local-batch.diff.
This version of batch mode has a couple distinguishing features:
Write-batch records (almost) the entire sender side of the conversation
into one file. ("Almost" because it has
2004 Mar 10
0
RFE: create batch without patching
Hi,
Currently, rsync --write-batch creates the batch fileset and also
updates the destination. I suggest adding the ability to disable the latter.
Motivation: I wish to sync two large but similar directories residing in
different machines. There is a slow (dial-up) network connection between
the machines, but I have physical access to both. Thus, I would like to
create a batch fileset by