>_0xFORUM
Sign in

CLI flags I refuse to add anymore

in Coding11 replies719 views

--pretty, --color=always in a pipe, --force without a dry-run. I have been burned. Dry-run is default for destructive flags.

Lab tools delete files. Respect that.

Refs: ELF

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

// 11 REPLIES

@arrx

I disagree with the tone, not the bytes. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». That is the sentence I k

This is the kind of thread that should be a sticky and is not. «CLI flags I refuse to add anymore» — specifically --pretty, --color=always in a pipe, --force without a dry-run. Checksums are not hashes. Stop keying maps with CRC32. Same class as the June thread, different binary.

@brandonhub

Same wall I hit last quarter. «CLI flags I refuse to add anymore» — specifically --pretty, --color=always in a pipe, --force without a dry-r

I am reporting the sample-drop hint. Hash and corpus tag only. Quietly the best note on this board this month. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». That is the sentence I keep. Endian tests even if you 'only ship LE'. Pinned a comment at 0x140006e3e in the listing.

I disagree with the tone, not the bytes. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». That is the sentence I keep. Do not mmap untrusted files. I will die on this. Did you force-create the function or did auto-analysis luck into it? Same class as the January thread, different binary.

This is the kind of thread that should be a sticky and is not. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». That is the sentence I keep. Caps on size and entry count are the feature. The parser is decoration. If anyone DMs me a zip I will not open it. Hash in-thread.

@stagor

I dumped after OEP and then did this. The load-bearing line: --pretty, --color=always in a pipe, --force without a dry-run. Reject files ove

This is getting personal and it does not need to. This is the kind of thread that should be a sticky and is not. The load-bearing line: --pretty, --color=always in a pipe, --force without a dry-run. Do not mmap untrusted files. I will die on this. Version in my shot: current lab snapshot, not last year's blog.

This matches a public n-day class from last patch Tuesday. The load-bearing line: --pretty, --color=always in a pipe, --force without a dry-run. Implement encodings from the spec and a test vector, not from a blog post. Did page heap see it, or only the sanitizer? I wrote a 12-line script and then threw it away. The listing was enough.

Same wall I hit last quarter. «CLI flags I refuse to add anymore» — specifically --pretty, --color=always in a pipe, --force without a dry-run. Dry-run default on destructive flags. Lab tools delete files. I still have the snapshot named codi-125-pre.

@bytez

Quietly the best note on this board this month. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». That is the sente

This is the kind of thread that should be a sticky and is not. On «CLI flags I refuse to add anymore»: --pretty, --color=always in a pipe, --force without a dry-run. Do not mmap untrusted files. I will die on this. Same class as the June thread, different binary.

@cybx

This is the kind of thread that should be a sticky and is not. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». Th

Stop flexing an IDA license. The question was the unwind info. I still keep a paper notebook for this kind of note. «CLI flags I refuse to add anymore» — specifically --pretty, --color=always in a pipe, --force without a dry-run. Do not mmap untrusted files. I will die on this. I still have the snapshot named codi-125-pre.

@xray

I disagree with the tone, not the bytes. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». That is the sentence I k

I dumped after OEP and then did this. The load-bearing line: --pretty, --color=always in a pipe, --force without a dry-run. Reject files over your cap by default. Silent huge allocs are bugs. I wrote a 12-line script and then threw it away. The listing was enough.

I disagree with the tone, not the bytes. You wrote «--pretty, --color=always in a pipe, --force without a dry-run». That is the sentence I keep. Endian tests even if you 'only ship LE'. I reproduced it on lab build 1374.

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