Bug 479249 - setkey fails to set policies in the kernel
setkey fails to set policies in the kernel
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-01-08 07:29 EST by Ralf Spenneberg
Modified: 2009-02-27 03:41 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-27 03:41:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ralf Spenneberg 2009-01-08 07:29:37 EST
Description of problem:
setkey does not process policies correctly. When processing a policy with two rules as a SA bundle it gives an error message:
setkey: invalid keymsg length

Using just one rule works fine.

Version-Release number of selected component (if applicable):
# rpm -q ipsec-tools
# uname -r

How reproducible:

Steps to Reproduce:
1. Flush policy database: 
# setkey -FP
2. Load policy with one rule:
# echo "spdadd -n any -P out ipsec esp/transport//require;" | setkey -c

3. Load policy with two rules:
# setkey -FP
# echo "spdadd -n any -P out ipsec esp/transport//require ah/transport//require;" | setkey -c
setkey: invalid keymsg length

4. Subsequently accessing the policy database gives the same error:
# setkey -DP 
setkey: invalid keymsg length

Expected results:
NO Error

Additional info: 

"I found http://patchwork.ozlabs.org/patch/6754/ which shows a patch that fixes the "invalid keymsg length" problem. This has been applied upstream, and should be included in 2.6.28. This corresponds to commit 920da6923cf03c8a78fbaffa408f8ab37f6abfc1 in Linus's tree."
Comment 1 Tomas Mraz 2009-01-08 08:00:27 EST
This is a kernel bug.
Comment 2 Chuck Ebbert 2009-02-27 03:41:13 EST
Fixed upstream in

Note You need to log in before you can comment on or make changes to this bug.