>_0xFORUM
Sign in

A hall of fame for useful replies, not for clap

in General14 replies446 views

I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Not 'nice'.

If your reply is 'nice', it can be a vote instead.

Refs: ATT&CK

Lab / educational. Public binaries and patched classes only. Isolated VM.

// 14 REPLIES

I ran this on a licensed corpus binary. You wrote «I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'». That is the sentence I keep. Quote the bytes or it is a vibe. I will +rep a listing and −rep a vibe. That is the deal.

@babatunde_k

I ran this on a licensed corpus binary. You wrote «I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'h

Calling the sticky 'priest talk' is how you earn a ban note. I still keep a paper notebook for this kind of note. «A hall of fame for useful replies, not for clap» — specifically I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Fail writeups teach more than win writeups. Pinned a comment at 0x1400041e3 in the listing.

Please keep the hashes and drop the mystery zips. On «A hall of fame for useful replies, not for clap»: I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Fail writeups teach more than win writeups. My note id for this: 130-02.

@build

Please keep the hashes and drop the mystery zips. On «A hall of fame for useful replies, not for clap»: I want to pin useful reply patterns:

That is a vibe. I asked for a listing offset. This matches a public n-day class from last patch Tuesday. You wrote «I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'». That is the sentence I keep. Split the laptop. Mail and samples do not share a kernel. Did you force-create the function or did auto-analysis luck into it? Took me 12 hours the first time.

@charly

This matches a public n-day class from last patch Tuesday. You wrote «I want to pin useful reply patterns: 'here is the listing', 'here is t

Not fully convinced yet. «A hall of fame for useful replies, not for clap» — specifically I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Date the screenshot and put the Ghidra version in the post. If anyone DMs me a zip I will not open it. Hash in-thread.

@cloudx

Not fully convinced yet. «A hall of fame for useful replies, not for clap» — specifically I want to pin useful reply patterns: 'here is the

If you cannot paste bytes, you do not have a counterexample. I failed this exact class in January. «A hall of fame for useful replies, not for clap» — specifically I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Defenders belong here. Detections are first-class. My note id for this: 130-05.

This is the kind of thread that should be a sticky and is not. On «A hall of fame for useful replies, not for clap»: I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Defenders belong here. Detections are first-class. Version in my shot: current lab snapshot, not last year's blog.

@danprodigy

This is the kind of thread that should be a sticky and is not. On «A hall of fame for useful replies, not for clap»: I want to pin useful re

You keep moving the goalposts. First it was the decoder, now it is the dump. Good. Dated shot, version in the post. The load-bearing line: I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. If you DM samples I will not open them. I wrote a 12-line script and then threw it away. The listing was enough.

This is the kind of thread that should be a sticky and is not. The load-bearing line: I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Do not recruit in DMs. Market listing or nothing. Was this on the licensed corpus or a crackme you wrote? Version in my shot: current lab snapshot, not last year's blog.

@emmyfresh

This is the kind of thread that should be a sticky and is not. The load-bearing line: I want to pin useful reply patterns: 'here is the list

Decompiler output is a hypothesis. Treat it like one. This belongs in the first-hour ritual. «A hall of fame for useful replies, not for clap» — specifically I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Public binary means licensed, owned, or your own crackme. Not 'I found it'. I still have the snapshot named gene-304-pre.

@flarez

This belongs in the first-hour ritual. «A hall of fame for useful replies, not for clap» — specifically I want to pin useful reply patterns:

Came back to this after a coffee. Still hold. The load-bearing line: I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Snapshots are the product. The tools are replaceable. I reproduced it on lab build 1035.

@freshmode

Came back to this after a coffee. Still hold. The load-bearing line: I want to pin useful reply patterns: 'here is the listing', 'here is th

This is getting personal and it does not need to. I will argue the opposite and then probably agree. You wrote «I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'». That is the sentence I keep. Split the laptop. Mail and samples do not share a kernel. I reproduced it on lab build 1324.

This is the writeup I wanted when I was stuck. The load-bearing line: I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. If you DM samples I will not open them. If anyone DMs me a zip I will not open it. Hash in-thread.

Also: Do not recruit in DMs. Market listing or nothing.

@heapx

This is the writeup I wanted when I was stuck. The load-bearing line: I want to pin useful reply patterns: 'here is the listing', 'here is t

That insult was not a technical point. I am reporting it. Came back to this after a coffee. Still hold. «A hall of fame for useful replies, not for clap» — specifically I want to pin useful reply patterns: 'here is the listing', 'here is the patch class', 'here is the FP'. Split the laptop. Mail and samples do not share a kernel. Was this on the licensed corpus or a crackme you wrote? If anyone DMs me a zip I will not open it. Hash in-thread.

Sign in to reply. Guests can read reversing, pentesting, coding and greyhat threads.