A 'known-good' ISO library and the one ISO that was not

I failed this exact class in January. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. Do not detonate in Docker. Shared kernel. VMs for samples, containers for tools. Is the hang the incomplete patch, or a second bug? I still have the snapshot named tool-271-pre.

@kiber_lisa

I failed this exact class in January. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. Do not detonate in D

You are describing a live target. Stop. Patched class only. Same wall I hit last quarter. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. Tools snapshot in 8 minutes or you will not restore it. I still have the snapshot named tool-271-pre.

@analys

Same wall I hit last quarter. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. Tools snapshot in 8 minutes

Please keep the hashes and drop the mystery zips. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. Dirty VM means throw it. Do not apt upgrade a dirty box. Version in my shot: current lab snapshot, not last year's blog.

@authz

Please keep the hashes and drop the mystery zips. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. Dirty VM

Take the telegram pitch to the bin. Market listing or nothing. Good. Dated shot, version in the post. The load-bearing line: We hashed the ISOs. Transfer samples as a hashed read-only ISO. Not drag-drop. Version in my shot: current lab snapshot, not last year's blog.

I want the listing, not the decompiler story. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. Transfer samples as a hashed read-only ISO. Not drag-drop. My note id for this: 10f-12.

Also: Do not detonate in Docker. Shared kernel. VMs for samples, containers for tools.

@brycehub

I want the listing, not the decompiler story. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. T

Quote the bytes or sit down. I ran this on a licensed corpus binary. You wrote «We hashed the ISOs». That is the sentence I keep. PE-sieve is a lead. It is not a verdict. After you did that, did the decompiler pick it up or did you dump? Same class as the June thread, different binary.

The screenshot is the useful part of the post. The load-bearing line: We hashed the ISOs. Clipboard off on the detonation VM. I pasted a token once. I wrote a 12-line script and then threw it away. The listing was enough.

@citydude

The screenshot is the useful part of the post. The load-bearing line: We hashed the ISOs. Clipboard off on the detonation VM. I pasted a tok

You are treating a checksum as a signature again. I would have written the opposite conclusion a year ago. You wrote «We hashed the ISOs». That is the sentence I keep. FakeNet that can reach the internet is not a simulator. Same class as the January thread, different binary.

This belongs in the first-hour ritual. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. Tools snapshot in 8 minutes or you will not restore it. If anyone DMs me a zip I will not open it. Hash in-thread.

@resrch

This belongs in the first-hour ritual. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. Tools sn

That is not what the listing shows. You are arguing a vibe. I failed this exact class in January. You wrote «We hashed the ISOs». That is the sentence I keep. Clipboard off on the detonation VM. I pasted a token once. Version in my shot: current lab snapshot, not last year's blog.

I disagree with the tone, not the bytes. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. PE-sieve is a lead. It is not a verdict. I wrote a 12-line script and then threw it away. The listing was enough.

@sigmaxx

I disagree with the tone, not the bytes. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. PE-sie

I read the patch. You read a tweet. Those are not the same source. I tried the naive path first and wasted a morning. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. FakeNet that can reach the internet is not a simulator. Hash of the public file, or are we arguing a shape? I still have the snapshot named tool-271-pre.

@stack

I tried the naive path first and wasted a morning. On «A 'known-good' ISO library and the one ISO that was not»: We hashed the ISOs. FakeNet

This is the writeup I wanted when I was stuck. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. Dirty VM means throw it. Do not apt upgrade a dirty box. My note id for this: 10f-04.

@tango

This is the writeup I wanted when I was stuck. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs.

Call-convention guess is not evidence. Same wall I hit last quarter. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. FakeNet that can reach the internet is not a simulator. I reproduced it on lab build 1170.

Agreed on the class, not on the tool. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. Caps on the drop folder saved the box. The 4GB 'txt' was a dump. I will +rep a listing and −rep a vibe. That is the deal.

@wanx

Agreed on the class, not on the tool. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. Caps on t

Do not call people skids because they use Ghidra. I will argue the opposite and then probably agree. «A 'known-good' ISO library and the one ISO that was not» — specifically We hashed the ISOs. Transfer samples as a hashed read-only ISO. Not drag-drop. If anyone DMs me a zip I will not open it. Hash in-thread.