tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

ipsec: slight inconsistency

[Still inetd(8) related.]

I'm rewriting the inetd/ipsec code since some acrobatics are not really
needed but when wanting to use directly ipsec_set_policy(3) and
ipsec_dump_policy(3), there is a slight inconsistency.

The two functions are said "inverse" from each other but the problem is
that if one gives a delimiter to ipsec_dump_policy(3) that is neither
a blank nor a new line, the string obtained can not be an input
to ipsec_set_policy(3). So there are not really inverse from each other.

Wouldn't it be more logical whether to have no delimiter to
ipsec_dump_policy(3) (defaulting to '\n' for separating the elementary
statements) or to allow a delimiter to ipsec_set_policy(3) when parsing
the policy passed?
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

Home | Main Index | Thread Index | Old Index