User Controls

Do computer files contain identifyable data?

  1. #21
    NARCassist gollums fat coach
    lol, hold on, i was thinking of emma watson hahha. yeah forget it, movie looks shit.



    .
  2. #22
    SBTlauien African Astronaut
    Originally posted by -SpectraL A bird is a bird.
    A phone is a phone.
    A computer is a computer.

    This was your -SpectraL lesson for the day. Carry on, soldiers.

    An apple is a fruit, a banana is a fruit, and they are both food.

    An iPhone is a phone, a Gallaxy S8 is a phone, and they are both computers.
  3. #23
    NARCassist gollums fat coach
    Originally posted by SBTlauien An apple is a fruit, a banana is a fruit, and they are both food.

    An iPhone is a phone, a Gallaxy S8 is a phone, and they are both computers.

    computers can also be phones



    .
  4. #24
    SBTlauien African Astronaut
    Originally posted by NARCassist computers can also be phones



    .

    I agree.
  5. #25
    -SpectraL coward [the spuriously bluish-lilac bushman]
    He wasn't referring to a phone, he was referring to a PC computer. You people really are weird.
  6. #26
    benny vader YELLOW GHOST
    Originally posted by -SpectraL He wasn't referring to a phone, he was referring to a PC computer. You people really are weird.

    op said computer. in this context it means desktop, laptop, palmtop, cocktop etc etc included.
  7. #27
    NARCassist gollums fat coach
    even a fucking refrigerator is a computer these days.



    .
  8. #28
    benny vader YELLOW GHOST
    Originally posted by NARCassist even a fucking refrigerator is a computer these days

    no, they have computers in them but they arent computers.

    they dont do computations.
  9. #29
    NARCassist gollums fat coach
    Originally posted by benny vader no, they have computers in them but they arent computers.

    they dont do computations.

    well they do, any code they execute is a form of computation. they just don't have the input/output system like a personal computer has. i'm sure there would be a way that a keyboard could be hooked up and then they could be reprogrammed to do all sorts of things.




    .
  10. #30
    -SpectraL coward [the spuriously bluish-lilac bushman]
    Fact is, any file created on a PC desktop computer has ZERO proprietary information attached to it.
  11. #31
    Lanny Bird of Courage
    Originally posted by Ajax Do you really talk like this?

    When I'm talking about filesystems, yes? What else would I talk like?

    Originally posted by infinityshock simple answer, with a modern computer: yes

    What exactly are you basing this on?
  12. #32
    Ajax African Astronaut [rumor the placative aphakia]
    Originally posted by Lanny When I'm talking about filesystems, yes? What else would I talk like?

    I would keep the end-user in mind. Your response sounded a bit technical for a question posed by a layperson.
  13. #33
    SBTlauien African Astronaut
    Originally posted by -SpectraL Fact is, any file created on a PC desktop computer has ZERO proprietary information attached to it.

    Facts.
  14. #34
    -SpectraL coward [the spuriously bluish-lilac bushman]
    In a .NET executable, the PE code section contains a stub that invokes the CLR virtual machine startup entry, _CorExeMain or _CorDllMain in mscoree.dll, much like it was in Visual Basic executables. The virtual machine then makes use of .NET metadata present, the root of which, IMAGE_COR20_HEADER (also called "CLR header") is pointed to by IMAGE_DIRECTORY_ENTRY_COMHEADER[5] entry in the PE header's data directory. IMAGE_COR20_HEADER strongly resembles PE's optional header, essentially playing its role for the CLR loader.

    The CLR-related data, including the root structure itself, is typically contained in the common code section, .text. It is composed of a few directories: metadata, embedded resources, strong names and a few for native-code interoperability. Metadata directory is a set of tables that list all the distinct .NET entities in the assembly, including types, methods, fields, constants, events, as well as references between them and to other assemblies.
  15. #35
    Lanny Bird of Courage
    Originally posted by -SpectraL In a .NET executable, the PE code section contains a stub that invokes the CLR virtual machine startup entry, _CorExeMain or _CorDllMain in mscoree.dll, much like it was in Visual Basic executables. The virtual machine then makes use of .NET metadata present, the root of which, IMAGE_COR20_HEADER (also called "CLR header") is pointed to by IMAGE_DIRECTORY_ENTRY_COMHEADER[5] entry in the PE header's data directory. IMAGE_COR20_HEADER strongly resembles PE's optional header, essentially playing its role for the CLR loader.

    The CLR-related data, including the root structure itself, is typically contained in the common code section, .text. It is composed of a few directories: metadata, embedded resources, strong names and a few for native-code interoperability. Metadata directory is a set of tables that list all the distinct .NET entities in the assembly, including types, methods, fields, constants, events, as well as references between them and to other assemblies.

    If you knew what half those words meant you'd realize how stupid copy pasting a section of an irrelevant wikipedia article that happened to contain the word "metadata" makes you look
    The following users say it would be alright if the author of this post didn't die in a fire!
  16. #36
    -SpectraL coward [the spuriously bluish-lilac bushman]
    Originally posted by Lanny If you knew what half those words meant you'd realize how stupid copy pasting a section of an irrelevant wikipedia article that happened to contain the word "metadata" makes you look

    I posted what a Windows executable file consists of. As we can see, there is no proprietary information there.
  17. #37
    Lanny Bird of Courage
    Originally posted by -SpectraL I posted what a Windows executable file consists of. As we can see, there is no proprietary information there.

    "windows executable file" and ".NET executable" are two different things.
  18. #38
    Lanny Bird of Courage
    Also I have no idea what you think "proprietary information" means, but I know you're wrong about it.
    The following users say it would be alright if the author of this post didn't die in a fire!
  19. #39
    mashlehash victim of incest [my perspicuously dependant flavourlessness]
    Originally posted by Ajax

    Damn son.

    They fuck right?
  20. #40
    NARCassist gollums fat coach
    Originally posted by -SpectraL In a .NET executable, the PE code section contains a stub that invokes the CLR virtual machine startup entry, _CorExeMain or _CorDllMain in mscoree.dll, much like it was in Visual Basic executables. The virtual machine then makes use of .NET metadata present, the root of which, IMAGE_COR20_HEADER (also called "CLR header") is pointed to by IMAGE_DIRECTORY_ENTRY_COMHEADER[5] entry in the PE header's data directory. IMAGE_COR20_HEADER strongly resembles PE's optional header, essentially playing its role for the CLR loader.

    The CLR-related data, including the root structure itself, is typically contained in the common code section, .text. It is composed of a few directories: metadata, embedded resources, strong names and a few for native-code interoperability. Metadata directory is a set of tables that list all the distinct .NET entities in the assembly, including types, methods, fields, constants, events, as well as references between them and to other assemblies.

    copy/pasta, the realm of the try hard.

    https://en.wikipedia.org/wiki/Portable_Executable#.NET.2C_metadata.2C_and_the_PE_format



    .
Jump to Top