> security: policydb version 21 does not match my version range 15-20 > I've looked around a bit, and I think this is a kernel issue. The > current kernels in unstable simply don't know about version 21 and > cannot handle it.
Yes, 2.6.17 will not support a version 21 policy file - even 2.6.18rc6-git4 will not support it either! The appropriate patch for the kernel was posted to the kernel mailing list last month: http://www.uwsg.indiana.edu/hypermail/linux/kernel/0608.1/1296.html Presumably this will get merged before 2.6.18 which in turn will hopefully get into etch. Would it be safer to ship the policy configured to build a version 20 policy by default until a new kernel is in unstable? Regards sr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
