3 ms·

This argument makes no sense. Data coming to your network adapter is also "stitched together and fed".

by lostmsu 4mo ago

solid_fuel 4mo ago
> This argument makes no sense. Data coming to your network adapter is also "stitched together and fed". Try reading it from start to end, it will make more sense if you think about it. By the way, if your OS is taking untrusted data from the network, inserting it into an executable code page, and loading it into the CPU then you have some SERIOUS security issues.
- anuramat 4mo ago
  but it's all just bytes?
  - solid_fuel 4mo ago
    It's all bytes but untrusted user data is stored in memory pages which are not marked executable. The CPU physically will not run instructions which are in areas of memory which are not marked as executable. This is a foundational principal of computing security. > In computer security, executable-space protection marks memory regions as non-executable, such that an attempt to execute machine code in these regions will cause an exception. It relies on hardware features such as the NX bit (no-execute bit), or on software emulation when hardware support is unavailable. Software emulation often introduces a performance cost, or overhead (extra processing time or resources), while hardware-based NX bit implementations have no measurable performance impact. https://en.wikipedia.org/wiki/Executable-space_protection https://en.wikipedia.org/wiki/Executable-space_protection
    - anuramat 4mo ago
      yes, assuming bugs don't exist
      - solid_fuel 4mo ago
        Wow, you're halfway there. Yes, when user data gets loaded into an executable code page - which are reserved for command data - it is a bug. That is why LLMs - which intentionally mix user data and command data into the same space - ARE BROKEN BY DESIGN. Do you get it now? It is a bug, and it is a bug which is fundamental to the design of LLMs. There is no way to build one that does not do this.
        anuramat 4mo ago
        are all storage devices broken by design as well?
        solid_fuel 4mo ago
        Are you somehow under the impression that storage devices and LLMs fill the same purpose? That's a major misunderstanding. Here's a good starting point if you're struggling with the difference between a computation device and a storage device: https://en.wikipedia.org/wiki/Computer https://en.wikipedia.org/wiki/Computer
        anuramat 4mo ago
        are you under the impression that LLMs and operating systems fill the same purpose?

This argument makes no sense. Data coming to your network adapter is also "stitched together and fed".

by lostmsu 4mo ago

This argument makes no sense. Data coming to your network adapter is also "stitched together and fed".

> This argument makes no sense. Data coming to your network adapter is also "stitched together and fed". Try reading it from start to end, it will make more sense if you think about it. By the way, if your OS is taking untrusted data from the network, inserting it into an executable code page, and loading it into the CPU then you have some SERIOUS security issues.

anuramat 4mo ago
but it's all just bytes?
- solid_fuel 4mo ago
  It's all bytes but untrusted user data is stored in memory pages which are not marked executable. The CPU physically will not run instructions which are in areas of memory which are not marked as executable. This is a foundational principal of computing security. > In computer security, executable-space protection marks memory regions as non-executable, such that an attempt to execute machine code in these regions will cause an exception. It relies on hardware features such as the NX bit (no-execute bit), or on software emulation when hardware support is unavailable. Software emulation often introduces a performance cost, or overhead (extra processing time or resources), while hardware-based NX bit implementations have no measurable performance impact. https://en.wikipedia.org/wiki/Executable-space_protection https://en.wikipedia.org/wiki/Executable-space_protection
  - anuramat 4mo ago
    yes, assuming bugs don't exist
    - solid_fuel 4mo ago
      Wow, you're halfway there. Yes, when user data gets loaded into an executable code page - which are reserved for command data - it is a bug. That is why LLMs - which intentionally mix user data and command data into the same space - ARE BROKEN BY DESIGN. Do you get it now? It is a bug, and it is a bug which is fundamental to the design of LLMs. There is no way to build one that does not do this.
      - anuramat 4mo ago
        are all storage devices broken by design as well?
        solid_fuel 4mo ago
        Are you somehow under the impression that storage devices and LLMs fill the same purpose? That's a major misunderstanding. Here's a good starting point if you're struggling with the difference between a computation device and a storage device: https://en.wikipedia.org/wiki/Computer https://en.wikipedia.org/wiki/Computer
        anuramat 4mo ago
        are you under the impression that LLMs and operating systems fill the same purpose?