Hi, Thanks for your response. I have had a look in libvici.c and it is indeed dependent from strongswan's libraries.
In order not to reinvent the wheel maybe it would make sense to remove the GPL license from libvici.h in order to give people a chance to reimplement the libvici.c? I don't really like the idea to redesign a small library whose interface will be very similar to the existing one. What do you think? Emeric ----- Mail original ----- De: "Martin Willi" <[email protected]> À: "Emeric POUPON" <[email protected]> Cc: [email protected] Envoyé: Mardi 14 Avril 2015 12:55:45 Objet: Re: [strongSwan-dev] vici license question Hi Emeric, > If I use the provided low-level C API to exchange messages, I guess I > fall into the GPL license for the whole utility? Yes, I'd say so. I've considered using a more liberal license for libvici. But as it makes heavy use of the GPLv2 licensed libstrongswan, that is not really an option. > Since the wire format is documented, I would have to rewrite my own > custom low level library in order to communicate with strongSwan? Yes, or use the existing Python/Ruby libraries, which are for this very reason licensed under MIT. Regards Martin _______________________________________________ Dev mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/dev
