|
Post by AnthroHeart on Jun 22, 2021 2:54:02 GMT
A few things:
1) Where will you store, on the Magic Server, the Nesting and the Hashing Tree Files? They probably should be in separate folders, maybe like /srv/nesting and /srv/hashing 2) Can you create 100 Nesting Files of 1M Records Each? 3) Can you create 10 Hashing Files of 1M Records Each? 4) Can you use KangarooTwelve? 5) What is the best Hash Size to use? I read actually that KangarooTwelve tops out at 256-bits, so why would it let you create a 2048-bit Hash? 6) Please use: HASH0.TXT and NEST0.TXT notation, where INTENTIONS.TXT is bottom of Tree.
|
|
|
Post by reden on Jun 22, 2021 3:07:42 GMT
A few things: 1) Where will you store, on the Magic Server, the Nesting and the Hashing Tree Files? They probably should be in separate folders, maybe like /srv/nesting and /srv/hashing 2) Can you create 100 Nesting Files of 1M Records Each? 3) Can you create 10 Hashing Files of 1M Records Each? 4) Can you use KangarooTwelve? 5) What is the best Hash Size to use? I read actually that KangarooTwelve tops out at 256-bits, so why would it let you create a 2048-bit Hash? 6) Please use: HASH0.TXT and NEST0.TXT notation, where INTENTIONS.TXT is bottom of Tree. By records, do you mean that I should insert them into the database directly?
|
|
|
Post by AnthroHeart on Jun 22, 2021 3:08:47 GMT
A few things: 1) Where will you store, on the Magic Server, the Nesting and the Hashing Tree Files? They probably should be in separate folders, maybe like /srv/nesting and /srv/hashing 2) Can you create 100 Nesting Files of 1M Records Each? 3) Can you create 10 Hashing Files of 1M Records Each? 4) Can you use KangarooTwelve? 5) What is the best Hash Size to use? I read actually that KangarooTwelve tops out at 256-bits, so why would it let you create a 2048-bit Hash? 6) Please use: HASH0.TXT and NEST0.TXT notation, where INTENTIONS.TXT is bottom of Tree. By records, do you mean that I should insert them into the database directly? No. Records can also be in a text file. Think of a Database Table like a glorified CSV file. Though it's more than that.
|
|
|
Post by reden on Jun 22, 2021 3:13:01 GMT
On the hash size: I read that after 1536 bits, SHA-3 authors can't guarantee security against crack attacks. However, the hash should still be collision resistant.
|
|
|
Post by AnthroHeart on Jun 22, 2021 3:17:57 GMT
On the hash size: I read that after 1536 bits, SHA-3 authors can't guarantee security against crack attacks. However, the hash should still be collision resistant. They say KangarooTwelve is to SHA-3 what BLAKE2 is to BLAKE. So not sure.
|
|
|
Post by reden on Jun 22, 2021 3:29:56 GMT
If we begin at 0 and make 100 files, it will actually be 101. Do you want that?
|
|
|
Post by AnthroHeart on Jun 22, 2021 3:31:34 GMT
If we begin at 0 and make 100 files, it will actually be 101. Do you want that? Yeah. 0 is just the bottom of the tree that points to the INTENTIONS.TXT itself. What Hash Size are you going to use? And how will you make 11 Hashing files without it being manual? Can you write a script using the bash script looping I gave before, to pass in the output of Kangaroo12 into each iteration?
|
|
|
Post by AnthroHeart on Jun 22, 2021 3:51:32 GMT
I had a question. What if we wanted to chain NEST and HASH files together?
Like the user wants NEST Level 47 and HASH Level 5.
How could we HASH Five Levels from NEST47.TXT ?
So instead of INTENTIONS.TXT being the bottom of the HASHING Tree, it would be NEST47.TXT.
|
|
|
Post by AnthroHeart on Jun 22, 2021 3:52:12 GMT
So they can choose Nesting, Hashing, or both Nesting and Hashing. Also Neither.
|
|
|
Post by AnthroHeart on Jun 22, 2021 3:54:40 GMT
I had a question. What if we wanted to chain NEST and HASH files together? Like the user wants NEST Level 47 and HASH Level 5. How could we HASH Five Levels from NEST47.TXT ? So instead of INTENTIONS.TXT being the bottom of the HASHING Tree, it would be NEST47.TXT. Or maybe create 100 levels of Hashing? It would mirror the Nesting, but would be in Hashes. Then they could choose: Nesting or Nested-Hashing.
|
|
|
Post by reden on Jun 22, 2021 4:07:23 GMT
I had a question. What if we wanted to chain NEST and HASH files together? Like the user wants NEST Level 47 and HASH Level 5. How could we HASH Five Levels from NEST47.TXT ? So instead of INTENTIONS.TXT being the bottom of the HASHING Tree, it would be NEST47.TXT. More or less, and for the Hash, it would have to use that File.
|
|
|
Post by AnthroHeart on Jun 22, 2021 4:21:49 GMT
A few things: 1) Where will you store, on the Magic Server, the Nesting and the Hashing Tree Files? They probably should be in separate folders, maybe like /srv/nesting and /srv/hashing 2) Can you create 100 Nesting Files of 1M Records Each? 3) Can you create 10 Hashing Files of 1M Records Each? 4) Can you use KangarooTwelve? 5) What is the best Hash Size to use? I read actually that KangarooTwelve tops out at 256-bits, so why would it let you create a 2048-bit Hash? 6) Please use: HASH0.TXT and NEST0.TXT notation, where INTENTIONS.TXT is bottom of Tree. By records, do you mean that I should insert them into the database directly? Large amounts of data are sometimes better as files, rather than in Tables.
|
|
|
Post by reden on Jun 22, 2021 4:34:03 GMT
If we begin at 0 and make 100 files, it will actually be 101. Do you want that? Yeah. 0 is just the bottom of the tree that points to the INTENTIONS.TXT itself. What Hash Size are you going to use? And how will you make 11 Hashing files without it being manual? Can you write a script using the bash script looping I gave before, to pass in the output of Kangaroo12 into each iteration? What script? It might be possible. The steps are: 1) For a compressed Nest file, or any Hash compressed file, we take its hash. 2) Make a copy of the file, and rename it to the first or the next level in the chain. 3) Write a NEST0.TXT file, which contains the Intention, Repeated <x> amount of times. Can optionally be more. 4) 7z a the file to the copy of the Zip. This will take a little time. 5) Repeat. Can perhaps wrap this up into "no output", a progress bar, Hashed File <y> out of <z>, or more.
|
|
|
Post by AnthroHeart on Jun 22, 2021 11:39:42 GMT
Yeah. 0 is just the bottom of the tree that points to the INTENTIONS.TXT itself. What Hash Size are you going to use? And how will you make 11 Hashing files without it being manual? Can you write a script using the bash script looping I gave before, to pass in the output of Kangaroo12 into each iteration? What script? It might be possible. The steps are: 1) For a compressed Nest file, or any Hash compressed file, we take its hash. 2) Make a copy of the file, and rename it to the first or the next level in the chain. 3) Write a NEST0.TXT file, which contains the Intention, Repeated <x> amount of times. Can optionally be more. 4) 7z a the file to the copy of the Zip. This will take a little time. 5) Repeat. Can perhaps wrap this up into "no output", a progress bar, Hashed File <y> out of <z>, or more. This script: for n in {1..1000000}; do echo "INTENTIONS.TXT" >> HASH0.TXT; doneWhat I would do is create a script that runs from scratch. You don't have to pass in any parameters. So, let's do a Nesting-Hashing Script from the ground up. Here's the pseudo-code (we don't need 7z for such small datasets). Note, pseudo code is more for explaining than actual code. It may not all run as is: 1) For just HASH0.TXT: for n in {1..1000000}; do KangarooTwelve "INTENTIONS.TXT" >> HASH0.TXT; done2) Create outside loop for 1..100 files, variable i 3) Modify Script above into something like (be sure to specify the Hash Size): for n in {1..1000000}; do KangarooTwelve "HASH" + (i - 1) + ".TXT" >> "HASH" + i + ".TXT"; done4) Close/End variable i loop. For just Nesting Files, do 1-4 above, but without KangarooTwelve, using echo instead. I recommend starting with small values like 100 instead of 1M, just to make sure it works.
|
|
|
Post by reden on Jun 22, 2021 14:50:40 GMT
Should the root of the Hash tree be NEST100.TXT as opposed to the compressed Nesting file?
|
|