-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
Sincerely,
Gabriel
- --
// Gabriel VLASIU
//
// OpenGPG-KeyID : 0xE684206E
// OpenGPG-Fingerprint: 0C3D 9F8B 725D E243 CB3C 8428 796A DB1F E684 206E
// OpenGPG-URL : http://www.vlasiu.net/public.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFK8TyZeWrbH+aEIG4RAs4wAJ4goQlHM2FhDl5b32SBc2oHXHx2lACfdBf5
PIay16wasp2LaxwF8QnupzA=
=pYey
-----END PGP SIGNATURE-----
_______________________________________________
Users mailing list
[email protected]
https://lists.strongswan.org/mailman/listinfo/users
