Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-10-05 Thread rajeev nohria
I am all set after adding libatomic.so.1 in lib directory. On Tue, Oct 4, 2016 at 3:05 PM, rajeev nohria wrote: > Andreas, > > Thank you for all your help. I have compiled the Strongswan with > petalinux . Whenever I run the charon I get the following error. Is there >

Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-10-04 Thread rajeev nohria
Andreas, Thank you for all your help. I have compiled the Strongswan with petalinux . Whenever I run the charon I get the following error. Is there any flag I can add in makefile to get this fixed? #charon charon: error while loading shared libraries: libatomic.so.1: cannot open shared object

Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-09-16 Thread Andreas Steffen
Hi Rajeev, yes, you have to load the private key file in your management tool and transfer it via the VICI interface as a binary blob. Regards Andreas On 15.09.2016 21:20, rajeev nohria wrote: > Anderas, > > When using davici- > For the loading of private rsa keys, that has to be loaded

Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-09-15 Thread rajeev nohria
Anderas, When using davici- For the loading of private rsa keys, that has to be loaded like the certificate? Thanks, Rajeev On Thu, Sep 15, 2016 at 3:19 PM, rajeev nohria wrote: > Anderas, > > For the loading of private rsa keys, that has to be loaded like the >

Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-09-15 Thread rajeev nohria
Anderas, For the loading of private rsa keys, that has to be loaded like the certificate? Thanks, Rajeev On Thu, Aug 4, 2016 at 12:16 AM, Andreas Steffen < andreas.stef...@strongswan.org> wrote: > Hi Rajeev, > > different to the stroke protocol and ipsec.conf where the filename > of the

Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-08-03 Thread Andreas Steffen
Hi Rajeev, different to the stroke protocol and ipsec.conf where the filename of the certificate gets transferred via the stroke socket and the charon daemon loads the certificate, vici transfers the certificate itself either as a binary DER or a base64-endocded PEM blob. Thus your management

Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-08-03 Thread rajeev nohria
Thanks Andreas, It worked, I know started to implement in Davici. I had PSK working in Davici. With certificates, I am having following issue during parse_certs(). 09[LIB] file coded in unknown format, discarded 09[LIB] building CRED_CERTIFICATE - X509 failed, tried 4 builders

Re: [strongSwan] Strongswan 5.4 issue using certificates

2016-08-02 Thread Andreas Steffen
Hi, according to your log, the initiator and responder create their own Root CA certificate and store it locally in /usr/local/etc/swanctl/x509ca. Therefore it is not surprising that no trust into the received host certificate can be established because it has been signed with the private key of