Handover, Make

First, congratulations Junio, on taking over this stuff, and all the best. Second, the killer argument, in the 'Recursive Make ... harmful' is the basic one that Recursive Makes breaks up the dependancy graph, and almost guarentees that it is wrong unless you do a lot of work to fix that artifact.

Re: SHA1 hash safety

or a > header file that is duplicated for convenience, ...) -- mit freundlichen Grüßen, Brian. Dr. Brian O'Mahoney Mobile +41 (0)79 334 8035 Email: [EMAIL PROTECTED] Bleicherstrasse 25, CH-8953 Dietikon, Switzerland PGP Key fingerprint = 33 41 A2 DE 35 7C CE 5D F5 14 39 C9 6D 38 56 D5 -

Re: fix mktemp (remove mktemp ;)

fine - it's just that I am running an old > version of it on one of my systems. Newer versions of the mktemp -t > option. > -- mit freundlichen Grüßen, Brian. Dr. Brian O'Mahoney Mobile +41 (0)79 334 8035 Email: [EMAIL PROTECTED] Bleicherstrasse 25, CH-8953 Dietikon, Sw

Re: SHA1 hash safety

Please see below: C. Scott Ananian wrote: > On Sat, 16 Apr 2005, Brian O'Mahoney wrote: > >> (1) I _have_ seen real-life collisions with MD5, in the context of >>Document management systems containing ~10^6 ms-WORD documents. > > > Dude! You could have be

Re: SHA1 hash safety

Three points: (1) I _have_ seen real-life collisions with MD5, in the context of Document management systems containing ~10^6 ms-WORD documents. (2) The HMAC (ethernet-harware-address) of any interface _should_ help to make a unique Id. (3) While I havn't looked at the details of the plumbi