__
Type your response ABOVE THIS LINE to reply
Customer: Aurender Support
Subject: Request for GPL source code of your Aurender A10 product
Eric Shim | DEC 31, 2017 | 09:55PM KST
Hi Max,
I have sent this email about a week ago, but looks like return email address
was not correct. So, I am send this again.
Here is s the instruction to build exact same binary from our source.
Please let us know if you have any issue.
1. rootfs for ubuntu 13.10
- Download rootfs
wget http://beta.aurender.com/gcc/ubuntu-aurender-13.10-i386-withmpd.tar.gz
- Make root directory for rootfs
mkdir root
- Extract file to root directory
sudo tar xzpf ubuntu-aurender-13.10-i386-withmpd.tar.gz -C root
- Bind local computer with this virtual roofs
sudo mount —bind /dev root/dev
sudo mount —bind /proc root/proc
sudo mount —bind /sys root/sys
sudo mount —bind /run root/run
- Now chroot to it
sudo chroot root
2. Build MPD
- Change directory to mpd
root@ubuntu:/# cd mpd/
- Just call builid.sh
root@ubuntu:/mpd# ./build.sh
- You will get below results.
>>> Strip : MPD
>>> Change Build ID: 9c575273c8446d4ba95b496a4fef8cfb0cdb32a7
>>> Now sha256sum is…
83f46f0eefd78e9cf6afa56d4065688806a73e486a4ffb5b008bbbe72ed3e382 src/mpd
3. Build-ID problem
Using the same development environment, you can get the same binary as you want
by generating same config.h for mpd.
However, sha256sum might be different because it removes the mpd binaries, has
the same file size, and gets the same unassembled results, but the build IDs
for elf binaries are different.
Since the "- enable-linker-build-id" option of configure is enabled, We could
not remove the Build ID or fix it as we wanted.
I do not know how this Build ID was randomly generated. As far as I know, it is
created with the same value on the same computer.
I included change_build_id.c and excute this program, it just changed the Build
ID in the notes section of the mpd elf binary.
So with this program, we patched the build ID of mpd which provided to you so
that you can get the sha256sum as you want.
Best regards,
Eric Shim
Eric Shim | DEC 24, 2017 | 10:41AM KST
Hi Max,
Here is s the instruction to build exact same binary from our source.
Please let us know if you have any issue.
1. rootfs for ubuntu 13.10
- Download rootfs
wget
http://beta.aurender.com/gcc/ubuntu-aurender-13.10-i386-withmpd.tar.gz
- Make root directory for rootfs
mkdir root
- Extract file to root directory
sudo tar xzpf ubuntu-aurender-13.10-i386-withmpd.tar.gz -C root
- Bind local computer with this virtual roofs
sudo mount --bind /dev root/dev
sudo mount --bind /proc root/proc
sudo mount --bind /sys root/sys
sudo mount --bind /run root/run
- Now chroot to it
sudo chroot root
2. Build MPD
- Change directory to mpd
root@ubuntu:/# cd mpd/
- Just call builid.sh
root@ubuntu:/mpd# ./build.sh
- You will get below results.
>>> Strip : MPD
>>> Change Build ID: 9c575273c8446d4ba95b496a4fef8cfb0cdb32a7
>>> Now sha256sum is...
83f46f0eefd78e9cf6afa56d4065688806a73e486a4ffb5b008bbbe72ed3e382 src/mpd
3. Build-ID problem
Using the same development environment, you can get the same binary as
you want by generating same config.h for mpd.
However, sha256sum might be different because it removes the mpd binaries, has
the same file size, and gets the same unassembled results, but the build IDs
for elf binaries are different.
Since the "- enable-linker-build-id" option of configure is enabled, We could
not remove the Build ID or fix it as we wanted.
I do not know how this Build ID was randomly generated. As far as I know, it is
created with the same value on the same computer.
I included change_build_id.c and excute this program, it just changed the Build
ID in the notes section of the mpd elf binary.
So with this program, we patched the build ID of mpd which provided to you so
that you can get the sha256sum as you want.
Best regards,
Eric Shim
Eric Shim | DEC 22, 2017 | 10:50AM KST
Hi Max,
Thank you for the explanation.
Can you please tell me the last file I sent (wimp.tar.gz) is matching to the
libwimp.so.1?
I have built and checked SHA and it matched. And you
