Lionel points to the use of insmod where modprobe should be used in racoon's setup.
Ganesan reports their belief in a fix of this in ipsec-tools 1:0.6.4-1 However, /usr/sbin/racoon-tool, which is the origin of thi bug, is not listed as part of ipsec-tools, AFAICS. Indeed, racoon-tools still calls "/sbin/insmod" explicitly (near line 2400). So how does ipsec-tools fix a bug in a different package (racoon)? Or am I missing something? -- Georg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
