b7kich

10 ms·

1. 1.▲
   by b7kich 10mo ago

   .kk
2. 2.▲
   by b7kich 2y ago

   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: expect
3. 3.▲
   by b7kich 2y ago

   May or may not be related: https://www.linkedin.com › crazytan Jia Tan - Snowflake | LinkedIn
4. 4.▲
   Free Bradley Manning(petitions.whitehouse.gov)

   2 points by b7kich 13y ago|0 comments
5. 5.▲
   by b7kich 14y ago

   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 request anyhow.
6. 6.▲
   by b7kich 14y ago

   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.
7. 7.▲
   by b7kich 14y ago

   Great read. Thanks for sharing!
8. 8.▲
   by b7kich 14y ago

   github + developers + visualization = kudos!