Bug 153723 - ifcfg-ipsec fails due to invalid keylength
ifcfg-ipsec fails due to invalid keylength
Status: CLOSED DUPLICATE of bug 150552
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-05 07:08 EDT by Marco Verleun
Modified: 2014-03-16 22:53 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-05 14:06:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marco Verleun 2005-04-05 07:08:00 EDT
Description of problem:
ifup-ipsec fails due to an invalid keylength error.

Version-Release number of selected component (if applicable):


How reproducible:
Reproducible by sourcing an config file, in my case .
/etc/sysconfig/networking-scripts/ifcfg-IPSec, and to evaluate the output of
every single line. Feeding this info into setkey -c results in an error message
invalid keylength.


Steps to Reproduce:
1.# . /etc/sysconfig/network-scripts/ifcfg-IPSec
2.# echo ${KEY_ESP_IN:+add $DST $SRC esp $SPI_ESP_IN -E
${ESP_PROTO_IN:-$ESP_PROTO} $(echo '"')$KEY_ESP_IN$(echo '"');}
3.# setkey -c
add 192.168.65.237 192.168.5.2 esp 0x201 -E 3des-cbc
"0x7aeaca3f87d060a12f4a4487d5a5c3355920fae69a96c831";

Actual results:
400 192 192
line 1: Invalid key length at [0x7aeaca3f87d060a12f4a4487d5a5c3355920fae69a96c83
1]

Expected results:
Silent acceptence of the command

Additional info:
Note the following does work:
1.# . /etc/sysconfig/network-scripts/ifcfg-IPSec
2.# echo ${KEY_ESP_IN:+add $DST $SRC esp $SPI_ESP_IN -E
${ESP_PROTO_IN:-$ESP_PROTO} $(echo '"')$KEY_ESP_IN$(echo '"');}
3.# setkey -c
add 192.168.65.237 192.168.5.2 esp 0x201 -E 3des-cbc
0x7aeaca3f87d060a12f4a4487d5a5c3355920fae69a96c831;
Comment 1 Marco Verleun 2005-04-05 07:12:24 EDT
Just in case the difference between the two commands is not clear I would like
to mention that the working example doesn't have the surrounding quotes.
Comment 2 Bill Nottingham 2005-04-05 14:06:11 EDT

*** This bug has been marked as a duplicate of 150552 ***

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