Due to the fact embedded software is distributed as signed and "locked down" images, GPLv3 components such as rsync cannot be meaningfully be made user-replaceable like the GPLv3 license requires (see Tivoization).
Hence it becomes impossible to legally ship rsync in most embedded software systems.
Is there a solution for this other than to not use rsync in this case?
Is GPLv3 really necessary for rsync? Or can it be relaxed to GPLv2?
Due to the fact embedded software is distributed as signed and "locked down" images, GPLv3 components such as
rsynccannot be meaningfully be made user-replaceable like the GPLv3 license requires (see Tivoization).Hence it becomes impossible to legally ship
rsyncin most embedded software systems.Is there a solution for this other than to not use
rsyncin this case?Is GPLv3 really necessary for
rsync? Or can it be relaxed to GPLv2?