Re: [avr-chat] µC/avr crypto lib

[Bob Blick]

Hi Eric,

Ahh, back to reasonable discourse. Good.

So how can we license code and insure that improvements to it go back to
the community, while still allowing it to be used in a proprietary
system? Because I can see how this is almost the opposite of the
personal computer, where the hardware is mostly generic and software can
be installed by users.

And in the embedded system, the software is fixed in the machine and
license violations are basically undetectable once the code is compiled,
optimized and linked.

I understand the GPL is based on strict principles. What compromises do
BSD and LGPL make, and what are their differences? Because holding Apple
up as a shining example of why the BSD license is good has the opposite
effect on me.

Cheerful regards,

Bob


Weddington, Eric wrote:

> Here's the difference: AVR software is tightly coupled to the
> underlying hardware used in embedded systems. The type of software
> that is typically GPLed and used by millions is for general-purpose
> computers: PCs running Linux, with all the various GNU software.
> Embedded systems are typically proprietary, and they're certainly not
> very general purpose. These proprietary systems are typically built
> by commercial entities which has interest in certain part of the
> software, whether for intellectual property (IP) or trade secrets, or
> at the least for competitive advantages. They won't use GPL software.
> The potential user base for GPL crypto code for the AVR is tiny, at
> best. It will very likely stay a curiosity. It certainly will not
> foster "community development". The community will consist of
> students and hobbyists.
> 
> But as it has been pointed out, there are alternatives such as
> LibTomCrypt, though AFAIK it has yet to be ported or vetted for the
> AVR.
>