full-disclosure - Re: FrSIRT False Alarm

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]

Date: Mon Aug 22 19:59:34 2005
From: davek_throwaway at hotmail.com (Dave Korn)
Subject: Re: FrSIRT False Alarm

----Original Message----
>From: Paul
>Message-Id: 009f01c5a5b1$2e3b4d80$6a01a8c0@...ls1337laptop

> Not to mention this is hardly even assembly. This is like really ghetto
> assembly. In REAL assembly, there would be no ".if" statements. It's all
> cmp blah blah, jz, jnz, etc. Lot's more work. Also, there is no such
> thing as .invoke MessageBox. Give me a break. In real assembly, that code
> would be about 5 times longer.

  Umm, this really just suggests that you aren't aware of the past thirty
years worth of advances in assembler technology.  Assemblers have had macro
functionality since as far back as anyone can remember, your claim that a
programmer should write everything out longhand is just ridiculous.  It's
like suggesting that nobody should use "#define" in C because it's cheating.
And hey, don't use loops, write the instruction sequence over and over again
by hand.  Don't use subroutines either, that's cheating too!  Of course, in
my day, we had nothing but front panel switches, and we had to toggle them
with our bare teeth, and father would  make us get oop at six o'clock in 't
morning and conduct electricity to computer using our own arms and legs for
power cables........

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