full-disclosure - Re: ndisasm bad opcodes interpretation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: davek_throwaway at hotmail.com (Dave Korn)
Subject: Re: ndisasm bad opcodes interpretation

"shadown" <shadown@...il.com> wrote in message
news:d8360fbf0501070830475ef080@...l.gmail.com...

>
> i.e:
> 0000001C 7565 jnz 0x83
> sould had been jnz 0x65

  No it shouldn't. Engage brain before opening mouth:  what is 0x65 + 0x1e
(== address of byte immediately after the instruction in question)?  Google
"pc-relative branch displacement" for more.  Or learn some assembler
programming before trying to use a disassembler.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....