Thanks you ! But How to deal with this problem? The configure followed from openswan.pdf handbook. Because my private key has password protected. When this error occurred, The ipsec auto --listall command shows like below: Apr 01 15:53:23 2009, 1024 RSA Key AwEAAdOVn (has private key), until Mar 31 17:29:00 2010 ok
-----邮件原件----- 发件人: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] 代表 Kyle Hamilton 发送时间: 2009年4月1日 15:59 收件人: openssl-users@openssl.org 主题: Re: Checking for RSA private key (/etc/ipsec.secrets) [DISABLED] This is certainly a configuration issue with S/WAN. I've never even heard of this. -Kyle H On Tue, Mar 31, 2009 at 11:50 PM, shawnlau <net17shawn...@gmail.com> wrote: > Hi all! > > > > > > When I use the x509 certification to connection two network, For I have set > the password for private key, So I add the line > > > > : RSA /etc/ipsec.d/private/right.key “passwd” to /etc/ipsec.secrets file. > > > > After that , I restart ipsec service , and checked the ipsec status by > command ipsec verify. Then: > > > > Checking your system to see if IPsec got installed and started correctly: > > Version check and ipsec on-path [OK] > > Linux Openswan U2.6.20/K2.6.18-92.1.22.el5 (netkey) > > Checking for IPsec support in kernel [OK] > > NETKEY detected, testing for disabled ICMP send_redirects > [OK] > > NETKEY detected, testing for disabled ICMP accept_redirects > [OK] > > Checking for RSA private key (/etc/ipsec.secrets) > [DISABLED] > > Checking that pluto is running [OK] > > Two or more interfaces found, checking IP forwarding > [OK] > > Checking NAT and MASQUERADEing > > Checking for 'ip' command [OK] > > Checking for 'iptables' command [OK] > > > > Is there any question in my openswan or it’s normal. > > > > Best regards! > > > > Shawn > > > > :I"rض ZK+1x˥[zZ fyҲӝfz{ ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
