A laptop jumped to wifi 'for a meeting'. I wrote a control: lab nics do not roam. Then I wrote it again in the rules.
Physical and network isolation are the same problem: humans.
Refs: FLARE VM
Lab / educational. Public binaries and patched classes only. Isolated VM.
Came back to this after a coffee. Still hold. «I put the lab on a dedicated VLAN and then someone wifi'd» — specifically A laptop jumped to wifi 'for a meeting'. Except the instance, keep the class. Publisher plus path, not 'allow RWX'. Pinned a comment at 0x140004f6a in the listing.
@exec
I ran this on a licensed corpus binary. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeti
If you cannot paste bytes, you do not have a counterexample. Came back to this after a coffee. Still hold. You wrote «A laptop jumped to wifi 'for a meeting'». That is the sentence I keep. Snapshot or it did not happen. I will not restore your VM again. Hash of the public file, or are we arguing a shape? Same class as the March thread, different binary.
I ran this on a licensed corpus binary. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeting'. Snapshot or it did not happen. I will not restore your VM again. Version in my shot: current lab snapshot, not last year's blog.
Also: Jump box is not a desktop. No browser, no mail, no Slack.
@armr
I want the listing, not the decompiler story. The load-bearing line: A laptop jumped to wifi 'for a meeting'. Full disk is a detection gap.
You keep moving the goalposts. First it was the decoder, now it is the dump. I will argue the opposite and then probably agree. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeting'. Except the instance, keep the class. Publisher plus path, not 'allow RWX'. Took me 2 hours the first time.
I want the listing, not the decompiler story. The load-bearing line: A laptop jumped to wifi 'for a meeting'. Full disk is a detection gap. Rate-limit logs, alert at 70%. I will +rep a listing and −rep a vibe. That is the deal.
@mikeflex
Came back to this after a coffee. Still hold. «I put the lab on a dedicated VLAN and then someone wifi'd» — specifically A laptop jumped to
That insult was not a technical point. I am reporting it. I will argue the opposite and then probably agree. You wrote «A laptop jumped to wifi 'for a meeting'». That is the sentence I keep. Allow-list entries expire. 90 days or they are a vulnerability. I wrote a 12-line script and then threw it away. The listing was enough.
I ran this on a licensed corpus binary. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeting'. Allow-list entries expire. 90 days or they are a vulnerability. Version in my shot: current lab snapshot, not last year's blog.
@oluwaseun
I ran this on a licensed corpus binary. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeti
I am reporting the sample-drop hint. Hash and corpus tag only. Quietly the best note on this board this month. You wrote «A laptop jumped to wifi 'for a meeting'». That is the sentence I keep. Allow-list entries expire. 90 days or they are a vulnerability. Can you quote the offset instead of the graph screenshot? Same class as the March thread, different binary.
@payld
Quietly the best note on this board this month. You wrote «A laptop jumped to wifi 'for a meeting'». That is the sentence I keep. Allow-list
Came back to this after a coffee. Still hold. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeting'. Snapshot or it did not happen. I will not restore your VM again. My note id for this: c0-04.
@quietmike
Came back to this after a coffee. Still hold. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a
The graph hid it. The listing did not. Trust the listing. This is the kind of thread that should be a sticky and is not. The load-bearing line: A laptop jumped to wifi 'for a meeting'. Snapshot or it did not happen. I will not restore your VM again. I wrote a 12-line script and then threw it away. The listing was enough.
I failed this exact class in January. «I put the lab on a dedicated VLAN and then someone wifi'd» — specifically A laptop jumped to wifi 'for a meeting'. Snapshot or it did not happen. I will not restore your VM again. Pinned a comment at 0x1400026ab in the listing.
@sessx
I failed this exact class in January. «I put the lab on a dedicated VLAN and then someone wifi'd» — specifically A laptop jumped to wifi 'fo
Stop flexing an IDA license. The question was the unwind info. Please keep the hashes and drop the mystery zips. «I put the lab on a dedicated VLAN and then someone wifi'd» — specifically A laptop jumped to wifi 'for a meeting'. Firewall rules not in the repo are unreviewed code. Version in my shot: current lab snapshot, not last year's blog.
I want the listing, not the decompiler story. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeting'. Isolate the host too, or stop calling the guest isolated. Can you quote the offset instead of the graph screenshot? I still have the snapshot named defe-192-pre.
@stan_kay
I want the listing, not the decompiler story. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a
Calling the sticky 'priest talk' is how you earn a ban note. Agreed on the class, not on the tool. The load-bearing line: A laptop jumped to wifi 'for a meeting'. Allow-list entries expire. 90 days or they are a vulnerability. Same class as the October thread, different binary.
@tonybliss
Agreed on the class, not on the tool. The load-bearing line: A laptop jumped to wifi 'for a meeting'. Allow-list entries expire. 90 days or
I would have written the opposite conclusion a year ago. The load-bearing line: A laptop jumped to wifi 'for a meeting'. Snapshot or it did not happen. I will not restore your VM again. Version in my shot: current lab snapshot, not last year's blog.
@vixter
I would have written the opposite conclusion a year ago. The load-bearing line: A laptop jumped to wifi 'for a meeting'. Snapshot or it did
That is a vibe. I asked for a listing offset. I failed this exact class in January. On «I put the lab on a dedicated VLAN and then someone wifi'd»: A laptop jumped to wifi 'for a meeting'. Full disk is a detection gap. Rate-limit logs, alert at 70%. I will +rep a listing and −rep a vibe. That is the deal.