Skip to the content ForoHackers
Log inJoin

My release can reproduce Tuesday. It can't spell the artist's name on Wednesday either.

Build systemsSupply chain security
#15331 · · Quote · Report

Our club's little puzzle game builds identically in two clean directories. Matching bytes, matching hashes, one identical typo in the end credits. I was the person recording the name from a handwritten note. The artist says she recognises the game as ours because we've been getting that particular vowel wrong since we were fifteen.

#15390 · · Quote · Report

A mí me gustan esos hashes iguales, ojo. Dicen qué se comparó. No saben si pusiste bien el nombre de tu amiga dos veces o si la cagaste dos veces. ¿Te mandó ella cómo quiere aparecer en el crédito?

#15391 · · Quote · Report

She has. Privately and without the chirpy pronunciation guide which I'd begun to compose in my head. I should probably let her keep the accent and let myself keep quiet.

#15392 · · Quote · Report

si vais a arreglarlo en el origen, que lea ella el crédito nuevo antes de sacar otra edición. dos copias de un nombre mal escrito no hacen mayoría.

#15393 · · Quote · Report

Are you planning to silently replace Tuesday's download? I already have it. I'd quite like to tell the fixed version from my old one without playing nine levels.

#15394 · · Quote · Report

New version. Original file keeps its digest. Changelog says correction to credits at the artist's request, no grand account of what the poor woman had for breakfast when I misheard her in 2008.

#15395 · · Quote · Report

Don't expect the fixed build to have Tuesday's hash. Compare the two clean builds of the fixed revision to each other. I know you know. I have also seen that test lovingly enforce the first typo forever.

#15402 · · Quote · Report

She played it. She reached the credits faster than I did, found the name right, then sent me a screenshot of my own high score in last place. Our friendship has returned to normal.

#15418 · · Quote · Report

Reproducible is handy, not an inspection of the contents. Two people can faithfully build the same typo. For exactly the same reason, two builds could faithfully reproduce a backdoor that was already in the source.

#15419 · · Quote · Report

I have made that slide for our next release meeting. The backdoor is hypothetical, the typo is extremely mine.

#15420 · · Quote · Report

Así sí tiene sentido publicar el parche del crédito y dejar que el siguiente compare las versiones. Si sólo cambias el fichero que ayer tenía otro contenido, el siguiente va a pensar que has vuelto a escribir mal su nombre.

#15421 · · Quote · Report

The artist is now credited correctly in my slides too. I had, I regret to inform you, managed to type it wrong a third time, this time in a talk about the patch.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply