[Pkg-swan-devel] [strongswan] 05/07: include curve25519 plugin.

[Yves-Alexis Perez]

On Fri, 2017-06-23 at 12:20 -0700, Gerald Turner wrote:
> Hello Yves-Alexis, today I got around to git-rebasing my own gbp repo
> with alioth's (first time using git-rebase, I love it!), and I noticed
> your commits 6ddc3ca3 ("include curve25519...") and 021aa5ad ("install
> libtpmtss...") were different than what I had done - should't curve25519
> be placed in libstrongswan-extra-plugins instead of libcharon-extra-
> plugins?  Conversely, while perhaps libtpmtss should have it's own
> package, I arbitrarily put it in libcharon-extra-plugins, whereas you
> put it in libstrongswan-extra-plugins.  My limited understanding of the
> distinction between libcharon and libstrongswan is that libstrongswan
> contains plugins for algorithms (like curve25519), URI fetchers and
> database layers, whereas libcharon contains plugins for kernel IPsec
> implementation glue, daemon glue (stroke/vici), authentication
> (EAP-xyz), and network tools (dhcp, farp, updown, etc).
> 
> I guess it doesn't matter, works either way, but which is correct?

Hi,

actually, you're correct, curve25519 is rather a libstrongswan than libcharon
plugin. We could still move it before it reaches testing.

About libtpmtss, I don't create a separate package because it's an internal
lib and I'd rather not create too many binary packages.

Regards,
-- 
Yves-Alexis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-swan-devel/attachments/20170626/727674da/attachment.sig>