.kk
Same here. The latest zilf is 0.9 https://foss.heptapod.net/zilf/zilf/-/releases >bin\Zilf.exe doomv109.zil ZILF 0.9 built 8/11/2019 4:30:42 AM [error MDL0128] doomv109.zil:1: ROOM: arg 1: expected ATOM [error MDL0113]…
May or may not be related: https://www.linkedin.com › crazytan Jia Tan - Snowflake | LinkedIn
How in the world would does the described issue with hash codes on distributed systems fix the issue of hash collisions in a request? Usually the attacker would send multiple parameters for "a","\0a","\00a" in a single…
Two wrongs don't make a right. The fact that "a".hash == "\0a" hash is an issue with the hash function. nothing else. Seeding the hash function so it is unique for each process does not solve the issue.
Great read. Thanks for sharing!
github + developers + visualization = kudos!
.kk
Same here. The latest zilf is 0.9 https://foss.heptapod.net/zilf/zilf/-/releases >bin\Zilf.exe doomv109.zil ZILF 0.9 built 8/11/2019 4:30:42 AM [error MDL0128] doomv109.zil:1: ROOM: arg 1: expected ATOM [error MDL0113]…
May or may not be related: https://www.linkedin.com › crazytan Jia Tan - Snowflake | LinkedIn
How in the world would does the described issue with hash codes on distributed systems fix the issue of hash collisions in a request? Usually the attacker would send multiple parameters for "a","\0a","\00a" in a single…
Two wrongs don't make a right. The fact that "a".hash == "\0a" hash is an issue with the hash function. nothing else. Seeding the hash function so it is unique for each process does not solve the issue.
Great read. Thanks for sharing!
github + developers + visualization = kudos!