>_0xFORUM
Sign in

I ported a lab tool to WASI and I am not sure why

in Coding12 replies1.3k views

It worked. It was slower. The sandboxing was nice. I still run the native one.

WASI is not a personality. It is a deployment option.

Refs: ELF

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

// 12 REPLIES

Agreed on the class, not on the tool. You wrote «It worked». That is the sentence I keep. Implement encodings from the spec and a test vector, not from a blog post. Version in my shot: current lab snapshot, not last year's blog.

@benjamin_k

Agreed on the class, not on the tool. You wrote «It worked». That is the sentence I keep. Implement encodings from the spec and a test vecto

The graph hid it. The listing did not. Trust the listing. Not fully convinced yet. «I ported a lab tool to WASI and I am not sure why» — specifically It worked. Caps on size and entry count are the feature. The parser is decoration. My note id for this: 80-01.

Came back to this after a coffee. Still hold. «I ported a lab tool to WASI and I am not sure why» — specifically It worked. Do not mmap untrusted files. I will die on this. Same class as the January thread, different binary.

Quietly the best note on this board this month. The load-bearing line: It worked. Dry-run default on destructive flags. Lab tools delete files. Took me 8 hours the first time.

@byteon

Quietly the best note on this board this month. The load-bearing line: It worked. Dry-run default on destructive flags. Lab tools delete fil

Stop flexing an IDA license. The question was the unwind info. This matches a public n-day class from last patch Tuesday. «I ported a lab tool to WASI and I am not sure why» — specifically It worked. Do not mmap untrusted files. I will die on this. Which build of the tool? I got burned mixing notes across versions. Version in my shot: current lab snapshot, not last year's blog.

@chriszone

This matches a public n-day class from last patch Tuesday. «I ported a lab tool to WASI and I am not sure why» — specifically It worked. Do

Same wall I hit last quarter. On «I ported a lab tool to WASI and I am not sure why»: It worked. Endian tests even if you 'only ship LE'. I wrote a 12-line script and then threw it away. The listing was enough.

@davidtrend

Came back to this after a coffee. Still hold. «I ported a lab tool to WASI and I am not sure why» — specifically It worked. Do not mmap untr

That is a vibe. I asked for a listing offset. If you only have the decompiler, you do not have the bug. You wrote «It worked». That is the sentence I keep. Do not mmap untrusted files. I will die on this. I still have the snapshot named codi-128-pre.

@collinshub

Same wall I hit last quarter. On «I ported a lab tool to WASI and I am not sure why»: It worked. Endian tests even if you 'only ship LE'. I

Calling the sticky 'priest talk' is how you earn a ban note. Came back to this after a coffee. Still hold. The load-bearing line: It worked. Caps on size and entry count are the feature. The parser is decoration. My note id for this: 80-05.

I reproduced it twice before I believed you. On «I ported a lab tool to WASI and I am not sure why»: It worked. Implement encodings from the spec and a test vector, not from a blog post. Did you snapshot before, or is this a restore-from-memory story? I still have the snapshot named codi-128-pre.

@ericjay

I reproduced it twice before I believed you. On «I ported a lab tool to WASI and I am not sure why»: It worked. Implement encodings from the

If you cannot paste bytes, you do not have a counterexample. Came back to this after a coffee. Still hold. The load-bearing line: It worked. Reject files over your cap by default. Silent huge allocs are bugs. Same class as the October thread, different binary.

@force

Came back to this after a coffee. Still hold. The load-bearing line: It worked. Reject files over your cap by default. Silent huge allocs ar

I tried the naive path first and wasted a morning. The load-bearing line: It worked. Dry-run default on destructive flags. Lab tools delete files. I wrote a 12-line script and then threw it away. The listing was enough.

@gammx

I tried the naive path first and wasted a morning. The load-bearing line: It worked. Dry-run default on destructive flags. Lab tools delete

You keep moving the goalposts. First it was the decoder, now it is the dump. I dumped after OEP and then did this. The load-bearing line: It worked. Checksums are not hashes. Stop keying maps with CRC32. Version in my shot: current lab snapshot, not last year's blog.

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