Embedding binary data in a script efficiently

前端 未结 2 573
故里飘歌
故里飘歌 2021-01-20 02:46

I have seen some installation files (huge ones, install.sh for Matlab or Mathematica, for example) for Unix-like systems, they must have embedded quite a lot of binary data,

相关标签:
2条回答
  • 2021-01-20 03:21

    You can use base64 + compression (using bz2 for instance) if that suits your data (e.g., if you're not embedding already compressed data).

    For instance, to create your data (say your data consist of 100 null bytes followed by 200 bytes with value 0x01):

    >>> import bz2
    >>> bz2.compress(b'\x00' * 100 + b'\x01' * 200).encode('base64').replace('\n', '')
    'QlpoOTFBWSZTWcl9Q1UAAABBBGAAQAAEACAAIZpoM00SrccXckU4UJDJfUNV'
    

    And to use it (in your script) to write the data to a file:

    import bz2
    data = 'QlpoOTFBWSZTWcl9Q1UAAABBBGAAQAAEACAAIZpoM00SrccXckU4UJDJfUNV'
    with open('/tmp/testfile', 'w') as fdesc:
        fdesc.write(bz2.decompress(data.decode('base64')))
    
    0 讨论(0)
  • 2021-01-20 03:29

    Here's a quick and dirty way. Create the following script called MyInstaller:

    #!/bin/bash
    
    dd if="$0" of=payload bs=1 skip=54
    
    exit
    

    Then append your binary to the script, and make it executable:

    cat myBinary >> myInstaller
    chmod +x myInstaller
    

    When you run the script, it will copy the binary portion to a new file specified in the path of=. This could be a tar file or whatever, so you can do additional processing (unarchiving, setting execute permissions, etc) after the dd command. Just adjust the number in "skip" to reflect the total length of the script before the binary data starts.

    0 讨论(0)
提交回复
热议问题