News for hackers. Stuff that matters.

b7kich

Re:RuBee on Monday November 24, 2025 @05:45AM (#46032572)
.kk
Re:Show HN: Wadzilla. Play DOOM in Zork on Friday May 31, 2024 @01:08PM (#40537663)
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] doomv109.zil:2: unrecognized value in DECL pattern: -48 [error MDL0215] doomv109.zil:2: GVAL: atom 'CEILING' has no global value

[error MDL0113] doomv109.zil:2: unrecognized value in DECL pattern: 80 [error MDL0113] doomv109.zil:3: unrecognized atom in DECL pattern: Unknown [error MDL0113] doomv109.zil:4: unrecognized atom in DECL pattern: Unknown [error MDL0113] doomv109.zil:5: unrecognized atom in DECL pattern: - [error MDL0113] doomv109.zil:17: unrecognized atom in DECL pattern: ROOM [error MDL0113] doomv109.zil:20: unrecognized value in DECL pattern: -48 [error MDL0215] doomv109.zil:20: GVAL: atom 'CEILING' has no global value

[error MDL0113] doomv109.zil:20: unrecognized value in DECL pattern: 80 [error MDL0113] doomv109.zil:21: unrecognized atom in DECL pattern: Unknown [error MDL0113] doomv109.zil:22: unrecognized atom in DECL pattern: Unknown [error MDL0113] doomv109.zil:23: unrecognized atom in DECL pattern: - [error MDL0113] doomv109.zil:47: unrecognized atom in DECL pattern: - [error MDL0128] doomv109.zil:48: GVAL: arg 1: expected ATOM

[error MDL0128] doomv109.zil:50: ROOM: arg 1: expected ATOM

[error MDL0113] doomv109.zil:51: unrecognized value in DECL pattern: 0 [error MDL0215] doomv109.zil:51: GVAL: atom 'CEILING' has no global value

>bin\Zilf.exe freedoom1.zil ZILF 0.9 built 8/11/2019 4:30:42 AM [error MDL0128] freedoom1.zil:1: ROOM: arg 1: expected ATOM

[error MDL0113] freedoom1.zil:2: unrecognized value in DECL pattern: 0 [error MDL0215] freedoom1.zil:2: GVAL: atom 'CEILING' has no global value

[error MDL0113] freedoom1.zil:2: unrecognized value in DECL pattern: 104 [error MDL0113] freedoom1.zil:3: unrecognized atom in DECL pattern: Unknown [error MDL0113] freedoom1.zil:4: unrecognized atom in DECL pattern: Unknown [error MDL0113] freedoom1.zil:5: unrecognized atom in DECL pattern: - [error MDL0113] freedoom1.zil:7: unrecognized atom in DECL pattern: STARGR1 [error MDL0215] <internally created FORM>: GVAL: atom 'Left' has no global value

[error MDL0113] freedoom1.zil:8: unrecognized atom in DECL pattern: SKSNAKE2 [error MDL0113] freedoom1.zil:9: unrecognized atom in DECL pattern: SKSNAKE2 [error MDL0113] freedoom1.zil:10: unrecognized atom in DECL pattern: SKSNAKE2 [error MDL0113] freedoom1.zil:11: unrecognized atom in DECL pattern: SKSNAKE2 [error MDL0113] freedoom1.zil:12: unrecognized atom in DECL pattern: ROOM [error MDL0113] freedoom1.zil:15: unrecognized value in DECL pattern: 0 [error MDL0215] freedoom1.zil:15: GVAL: atom 'CEILING' has no global value

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 request anyhow.
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.
Re:SPDY Review by Opera Software on Thursday June 07, 2012 @11:51AM (#4079579)
Great read. Thanks for sharing!
github + developers + visualization = kudos!