OpenSolaris

Printable Version Enter a New Search
Bug ID 6821894
Synopsis [CLI] - ipseckey and ipsecconf command output lists some unlocalized messages
State 3-Accepted (Yes, that is a problem)
Category:Subcategory network:ipsec
Keywords oss-bite-size
Sponsor
Submitter
Reported Against s10u7_07
Duplicate Of
Introduced In
Commit to Fix
Fixed In
Release Fixed
Related Bugs
Submit Date 25-March-2009
Last Update Date 20-August-2009
Description
platforms: both x86 and sparc platforms
languages: seen on FIGSCCJK languages

#ipseckey command outputs following messages are unlocalized:
- Diagnostic code 44: Bad number of authentication bits
- <ip address> already exists
- Fatal error exiting
- Diagnostic code 19: Missing destination address
- <ip address> does not exist
- Diagnostic code 78: Security association not found
- ipseckey: ERROR: <file> open error
- ipseckey: WARNING: Save file already exists with permission 644.
  ipseckey: Normal users may be able to read IPSec keying material.

Note:attached text file is the output of ipseckey command execution: ipseckey.txt

#ipsecconf command outputs following are unlocalized:

bash-3.00#export LC_ALL=fr_FR.UTF-8;LANG=fr_FR.UTF-8

bash-3.00# ipsecconf -a /etc/inet/ipsecinit.conf

        IPsec policy should be managed using smf(5). Modifying
        the IPsec policy from the command line while the 'policy'
        service is enabled could result in an inconsistent
        security policy.

ipsecconf: Renvoi du noyau: L'entr¿©e existe d¿©j¿ 
ipsecconf: Entr¿©e de strat¿©gie en double (ignor¿©e) :
{laddr fr1 raddr fr2} ipsec {auth_algs any encr_algs any sa shared}

        AVERTISSEMENT : L'ajout de nouvelles entr¿©es de strat¿©gies risque
        d'affecter les connexions existantes. Les connexions existantes
        qui ne sont pas soumises ¿  des contraintes de strat¿©gies risquent de
        l'¿"tre en raison des nouvelles
        strat¿©gies. Cela peut interrompre la communication entre les
        connexions existantes.

in above output : One para is not localized

bash-3.00# ipsecconf -f

        IPsec policy should be managed using smf(5). Modifying
        the IPsec policy from the command line while the 'policy'
        service is enabled could result in an inconsistent
        security policy.

bash-3.00# ipsecconf -F

        IPsec policy should be managed using smf(5). Modifying
        the IPsec policy from the command line while the 'policy'
        service is enabled could result in an inconsistent
        security policy.

Note: this is happening with FIGSCCJK languages
Work Around
N/A
Comments
N/A