Gabriel VLASIU wrote:
> Hi.
>
> On Wed, 4 Nov 2009, Andreas Steffen wrote:
>
>> have a look at the 4.3.5 ChangeLog:
>
>> - The private/public key parsing and encoding has been split up
>> into separate pkcs1, pgp, pem and dnskey plugins. The public key
>> implementation plugins gmp, gcrypt and openssl can all make use
>> of them.
>
>> This means that if you load your plugins via an explicit load=
>> statement in the pluto section of strongswan.conf you must include
>
>> pkcs1 pem
>
>> and you can omit the pubkey plugin.
>
> Thank you for your quick answer.
>
> My pluto section in strongswan.conf was like this:
>
> pluto {
>
> # plugins to load in pluto
> load = aes des sha1 sha2 md5 gmp random x509 pubkey hmac xcbc
> # stroke kernel-netlink updown
> }
>
> Adding "pkcs1 pem" to load statement solve my problem. Thank you.
>
> One more question: on a different computer with load statement in pluto
> section commented, I did not encountered such problem. Are pkcs1 and pem
> plugins loaded by default?
>
Yes, without an explicit load statement all necessary plugins are
loaded by default. A load statement makes only sense if you enabled
a lot of additional plugins (e.g. SQL or EAP plugins) during compile
time which you wouldn't want to be loaded during runtime. This is
the case e.g. in the Linux Distributions (Debian, Ubuntu, OpenSUSE)
which compile nearly all available strongSwan plugins.
> Sincerely,
> Gabriel
Regards
Andreas
======================================================================
Andreas Steffen [email protected]
strongSwan - the Linux VPN Solution! www.strongswan.org
Institute for Internet Technologies and Applications
University of Applied Sciences Rapperswil
CH-8640 Rapperswil (Switzerland)
===========================================================[ITA-HSR]==
_______________________________________________
Users mailing list
[email protected]
https://lists.strongswan.org/mailman/listinfo/users
