(no subject)

From: Wolfgang Schelongowski (spamtrap@xivic.prima.de)
Date: 10/30/02


From: spamtrap@xivic.prima.de (Wolfgang Schelongowski)
Date: 30 Oct 2002 20:22:08 +0100

In <868z0g3w7g.fsf@potato.vegetable.org.uk>
 Tim Haynes <usenet@stirfried.vegetable.org.uk> writes:

>spamtrap@xivic.prima.de (Wolfgang Schelongowski) writes:

[somebody else Tim graciously snipped wrote]
>>>> Can you give pointers to the source where it oversteps the bounds described
>>>> above?
>>
>> Where it says:
>> | To remind you, the DeScan listening
>> |agent is a very small binary
>>
>> Where's the source, man? IOW they don't reveal to us what they really do.
>> That's *B*A*D*.

>The source is right in front of your eyes.

Obviously you have no understanding of the basics of programming. So just
for you, in a nutshell:
 #include <linux/module.h>
 #include <linux/fs.h>
...
 static void sr_release(struct cdrom_device_info *cdi)
 {
        if (scsi_CDs[MINOR(cdi->dev)].sector_size > 2048)
                sr_set_blocklength(MINOR(cdi->dev),2048);
        sync_dev(cdi->dev);
        scsi_CDs[MINOR(cdi->dev)].device->access_count--;
        if (scsi_CDs[MINOR(cdi->dev)].device->host->hostt->module)
                __MOD_DEC_USE_COUNT(scsi_CDs[MINOR(cdi->dev)].device->host->host
        if(sr_template.module)
                __MOD_DEC_USE_COUNT(sr_template.module);
 }
is an example of a part of a source. In this context the file name
usually ends with ".c", and a compiler produces the binary from it.

>There's nothing wrong with use
>of the word `binary' when describing a binary.

I never said it was. But as long as they don't give us the source from
which it is compiled the only way to find out what the binary really
does is to disassemble it and ma nually decompile it. The latter is a
very timeconsuming operation which only very few programmers can do
successfully.

HTH. HAD.

-- 
"Some people are heroes. And some people jot down notes."
  -- Terry Pratchett, The Truth



Relevant Pages

  • (no subject)
    ... >> |agent is a very small binary ... IOW they don't reveal to us what they really do. ... Obviously you have no understanding of the basics of programming. ... and a compiler produces the binary from it. ...
    (comp.os.linux.security)
  • (no subject)
    ... >> |agent is a very small binary ... IOW they don't reveal to us what they really do. ... Obviously you have no understanding of the basics of programming. ... and a compiler produces the binary from it. ...
    (comp.security.firewalls)
  • (no subject)
    ... >> |agent is a very small binary ... IOW they don't reveal to us what they really do. ... Obviously you have no understanding of the basics of programming. ... and a compiler produces the binary from it. ...
    (comp.security.misc)
  • Re: [EGN] Numerical Accuracy
    ... The advice worked because in fact the Microsoft compiler had a bug. ... The capabilities of the optimizer are not so ... The language standard itself says ... of "programming" as a nonprofession. ...
    (comp.programming)
  • Re: why qwerty keyboard has NOT been used in ColorForth
    ... Forth minus source code and compiler and with a key table interpreter ... that could show dissasembled native opcodes and named Forth word ... The way Chuck put it, he wanted to explore the notion of reduced size ... It is what is known as bare metal programming. ...
    (comp.lang.forth)