Re: [bug #61594] suggest new $(hash ...) function

2021-12-06 Thread Tim Murphy
How does Python or Javascript manage with their map implementations that use a hash to select a bucket? One would want a low collision hash and that's really all that's needed to make unique filenames from input data that would be too long to just concatenate. Regards, Tim On Sun, 5 Dec 2021 at

RE: [bug #61594] suggest new $(hash ...) function

2021-12-02 Thread rsbecker
On December 2, 2021 4:20 AM, Boris Kolpackov > rsbec...@nexbridge.com writes: > > > Sadly, the import restrictions do not distinguish between message > > digests and cryptography [...] > > You seem to be quite knowledgeable on the matter so can you provide one > concrete example of where one jur

RE: [bug #61594] suggest new $(hash ...) function

2021-12-02 Thread rsbecker
On December 2, 2021 3:44 AM, Edward Welbourne > > My first counter-argument comes from the "$(shell git hash-object obj)" > > suggestion which begs the question: if git, which relies heavily upon > > SHA-1, is available, doesn't that mean SHA-1 is also natively > > available? I'm not aware of git b

Re: [bug #61594] suggest new $(hash ...) function

2021-12-02 Thread Boris Kolpackov
rsbec...@nexbridge.com writes: > Sadly, the import restrictions do not distinguish between message > digests and cryptography [...] You seem to be quite knowledgeable on the matter so can you provide one concrete example of where one jurisdiction restricts export to another of, say, an SHA-1 imp

Re: [bug #61594] suggest new $(hash ...) function

2021-12-02 Thread Edward Welbourne
> My first counter-argument comes from the "$(shell git hash-object obj)" > suggestion which begs the question: if git, which relies heavily upon SHA-1, > is available, doesn't that mean SHA-1 is also natively available? I'm not > aware of git being restricted in any jurisdictions. Seems unlikely,

RE: [bug #61594] suggest new $(hash ...) function

2021-12-01 Thread rsbecker
On December 1, 2021 9:42 AM, anonymous wrote: > These are all good and useful points, thanks. However, some counter- > arguments: > I tried to be careful to distinguish "cryptographic" from "low-collision-rate- > hash" in the original description because I absolutely do not want to > "introduce cry

RE: [bug #61594] suggest new $(hash ...) function

2021-12-01 Thread rsbecker
On December 1, 2021 9:06 AM, Tim Murphy wrote: > On Wed, 1 Dec 2021 at 12:37, Edward Welbourne > wrote: >> mailto:rsbec...@nexbridge.com (1 December 2021 13:08) wrote: >>> I would suggest that adding cryptography to GNU Make would limit its >>> reach. There are jur

Re: [bug #61594] suggest new $(hash ...) function

2021-12-01 Thread Tim Murphy
I have added such a function as a loadable library before - you might consider that if you can't get it done another way. https://github.com/tnmurphy/extramake look at hash.c. To try it : cd example && make -f example.mk > I called the function siphash24 because that's what I used - and its' d

Re: [bug #61594] suggest new $(hash ...) function

2021-12-01 Thread Edward Welbourne
rsbec...@nexbridge.com (1 December 2021 13:08) wrote: > I would suggest that adding cryptography to GNU Make would limit its > reach. There are jurisdictions where it is questionable to import > software containing any cryptography. In addition, there are numerous > tools for doing what you want.

RE: [bug #61594] suggest new $(hash ...) function

2021-12-01 Thread rsbecker
On November 30, 2021 11:37 PM, anonymous wrote: > To: psm...@gnu.org; bo...@kolpackov.net; bug-make@gnu.org > Subject: [bug #61594] suggest new $(hash ...) function > > URL: > > > Summary: suggest new $(hash ...) function >