Out-of-band patches: hunting who missed them

This is the writeup I wanted when I was stuck. You wrote «The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'». That is the sentence I keep. OOB read is a leak until proven otherwise. In the notes, not in a PoC. Took me 10 hours the first time.

I ran this on a licensed corpus binary. The load-bearing line: The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'. Date your heap notes. 2012 grooming diagrams are history. If anyone DMs me a zip I will not open it. Hash in-thread.

@guard

This is the writeup I wanted when I was stuck. You wrote «The forgot-VM problem is worse on out-of-band because the process is 'someone saw

You are treating a checksum as a signature again. I will argue the opposite and then probably agree. You wrote «The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'». That is the sentence I keep. No samples, even public corpus files. Hashes and links. Attachments get pulled. I reproduced it on lab build 1079.

@lockx

Bookmarking this for the lab wiki. «Out-of-band patches: hunting who missed them» — specifically The forgot-VM problem is worse on out-of-ba

That is not what the listing shows. You are arguing a vibe. I reproduced it twice before I believed you. On «Out-of-band patches: hunting who missed them»: The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'. Date your heap notes. 2012 grooming diagrams are history. Version in my shot: current lab snapshot, not last year's blog.

@idrisconnect

I ran this on a licensed corpus binary. The load-bearing line: The forgot-VM problem is worse on out-of-band because the process is 'someone

You skipped isolation and then asked why the box is dirty. That is on you. I ran this on a licensed corpus binary. On «Out-of-band patches: hunting who missed them»: The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'. A saturating add that hangs is not a complete patch. Hunt the hang too. Is the hang the incomplete patch, or a second bug? I still have the snapshot named expl-237-pre.

@kenwise

Not fully convinced yet. «Out-of-band patches: hunting who missed them» — specifically The forgot-VM problem is worse on out-of-band because

I am not moving this to DMs so you can yell. Stay on the class. Not fully convinced yet. «Out-of-band patches: hunting who missed them» — specifically The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'. A saturating add that hangs is not a complete patch. Hunt the hang too. I wrote a 12-line script and then threw it away. The listing was enough.

@jamesnode

I ran this on a licensed corpus binary. On «Out-of-band patches: hunting who missed them»: The forgot-VM problem is worse on out-of-band bec

Not fully convinced yet. «Out-of-band patches: hunting who missed them» — specifically The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'. A saturating add that hangs is not a complete patch. Hunt the hang too. I wrote a 12-line script and then threw it away. The listing was enough.

Bookmarking this for the lab wiki. «Out-of-band patches: hunting who missed them» — specifically The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'. Date your heap notes. 2012 grooming diagrams are history. If anyone DMs me a zip I will not open it. Hash in-thread.

This matches a public n-day class from last patch Tuesday. On «Out-of-band patches: hunting who missed them»: The forgot-VM problem is worse on out-of-band because the process is 'someone saw the mail'. Date your heap notes. 2012 grooming diagrams are history. Which build of the tool? I got burned mixing notes across versions. My note id for this: ed-08.