(racoon 866) problem-failed to open the backup file /etc/backupsa.conf.

  
Sir,

I have a problem ragarding the the Configuration and running of the Racoon(IKE- KAME-IPsec-.4b toos) , could you please give the information where the problem lies and how to fix the problem?

The problem


the racoon.conf file is as bolow

########################################################

path backupsa "/etc/backupsa.conf";
path pre_shared_key "/etc/psk.txt";
                                                                                                                             
remote 192.168.1.137 {
        exchange_mode main;
        proposal {
                encryption_algorithm 3des;
                hash_algorithm md5;
                authentication_method pre_shared_key;
                dh_group modp1024;
        }
}
                                                                                                                             
#sainfo address 192.168.1.138 any address 192.168.1.137 any {
 #       pfs_group modp768;
  #      encryption_algorithm 3des;
   #     authentication_algorithm hmac_md5;
    #    compression_algorithm deflate;
#}

#############################################################


When ever i run the racoon manulally by using the command

           # racoon -BdCFL -f /etc/racoon.conf

it is giving the messages like this mentioned below,
 
2004-11-24 11:07:39: ERROR: safefile.c:84:safefile(): /etc/backupsa.conf has weak file permission
2004-11-24 11:07:39: ERROR: backupsa.c:228:backupsa_from_file(): failed to open the backup file /etc/backupsa.conf.
racoon: something error happened SA recovering.


the below messages are dumped onto the console


//////#############################################################

Foreground mode.
2004-11-24 11:07:37: INFO: main.c:185:main(): @(#)ipsec-tools 0.4b1 (http://ipsec-tools.sourceforge.net)
2004-11-24 11:07:37: INFO: main.c:186:main(): @(#)This product linked OpenSSL 0.9.7a Feb 19 2003 (http://www.openssl.org/)
2004-11-24 11:07:37: DEBUG: pfkey.c:384:pfkey_init(): call pfkey_send_register for AH
2004-11-24 11:07:37: DEBUG: pfkey.c:384:pfkey_init(): call pfkey_send_register for ESP
2004-11-24 11:07:37: DEBUG: pfkey.c:384:pfkey_init(): call pfkey_send_register for IPCOMP
2004-11-24 11:07:37: DEBUG: cftoken.l:584:yycf_set_buffer(): reading config file /etc/racoon.conf
2004-11-24 11:07:37: INFO: remoteconf.c:396:dump_rmconf_single(): remote 192.168.1.137[500] {
2004-11-24 11:07:37: INFO: remoteconf.c:404:dump_rmconf_single():       exchange_type main;
2004-11-24 11:07:37: INFO: remoteconf.c:405:dump_rmconf_single():       doi ipsec_doi;
2004-11-24 11:07:37: INFO: remoteconf.c:432:dump_rmconf_single():       my_identifier address;
2004-11-24 11:07:37: INFO: remoteconf.c:438:dump_rmconf_single():       peers_identifier address;
2004-11-24 11:07:37: INFO: remoteconf.c:441:dump_rmconf_single():       send_cert on;
2004-11-24 11:07:37: INFO: remoteconf.c:443:dump_rmconf_single():       send_cr on;
2004-11-24 11:07:37: INFO: remoteconf.c:445:dump_rmconf_single():       verify_cert on;
2004-11-24 11:07:37: INFO: remoteconf.c:447:dump_rmconf_single():       verify_identifier off;
2004-11-24 11:07:37: INFO: remoteconf.c:449:dump_rmconf_single():       nat_traversal off;
2004-11-24 11:07:37: INFO: remoteconf.c:452:dump_rmconf_single():       nonce_size 16;
2004-11-24 11:07:37: INFO: remoteconf.c:454:dump_rmconf_single():       passive off;
2004-11-24 11:07:38: INFO: remoteconf.c:456:dump_rmconf_single():       initial_contact on;
2004-11-24 11:07:38: INFO: remoteconf.c:458:dump_rmconf_single():       generate_policy off;
2004-11-24 11:07:38: INFO: remoteconf.c:460:dump_rmconf_single():       support_proxy off;
2004-11-24 11:07:38: INFO: remoteconf.c:464:dump_rmconf_single():
2004-11-24 11:07:38: INFO: remoteconf.c:465:dump_rmconf_single():       /* prop_no=1, trns_no=1, rmconf=192.168.1.137[500] */2004-11-24 11:07:38: INFO: remoteconf.c:469:dump_rmconf_single():       proposal {
2004-11-24 11:07:38: INFO: remoteconf.c:470:dump_rmconf_single():               lifetime time 28800 sec;
2004-11-24 11:07:38: INFO: remoteconf.c:472:dump_rmconf_single():               lifetime bytes 0;
2004-11-24 11:07:38: DEBUG: algorithm.c:644:alg_oakley_dhdef(): hmac(modp1024)
2004-11-24 11:07:38: INFO: remoteconf.c:474:dump_rmconf_single():               dh_group modp1024;
2004-11-24 11:07:38: DEBUG: algorithm.c:403:alg_oakley_encdef(): encryption(3des)
2004-11-24 11:07:38: INFO: remoteconf.c:476:dump_rmconf_single():               encryption_algorithm 3des;
2004-11-24 11:07:38: DEBUG: algorithm.c:260:alg_oakley_hashdef(): hash(md5)
2004-11-24 11:07:38: INFO: remoteconf.c:478:dump_rmconf_single():               hash_algorithm md5;
2004-11-24 11:07:38: INFO: remoteconf.c:480:dump_rmconf_single():               authentication_method pre_shared_key;
2004-11-24 11:07:39: INFO: remoteconf.c:482:dump_rmconf_single():       }
2004-11-24 11:07:39: INFO: remoteconf.c:485:dump_rmconf_single(): }
2004-11-24 11:07:39: INFO: remoteconf.c:486:dump_rmconf_single():
2004-11-24 11:07:39: ERROR: safefile.c:84:safefile(): /etc/backupsa.conf has weak file permission
2004-11-24 11:07:39: ERROR: backupsa.c:228:backupsa_from_file(): failed to open the backup file /etc/backupsa.conf.
racoon: something error happened SA recovering.

###################################################### /////////////

so please give the solution to fix the error ragarding BACKUPSA

which ype of file is the "backupsa" ?
i mean   backupsa.txt  or  backupsa.conf
 

please give the solution as soon as possible sir,

thanking you,

Regards,
Saikrishna G