Bug 150552

Summary: ipsec limited to ascii only keys
Product: [Fedora] Fedora Reporter: Steven Whitehouse <steve>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: mverleun, riek, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 8.06-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-03-28 22:19:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
a patch for this none

Description Steven Whitehouse 2005-03-08 08:58:09 UTC 
Description of problem:

If you create a ifcfg-ipsec0 file, you can only specify keys
using ascii, not hex, due to quoting which is done in the ifup-ipsec
script. The ipsec HOWTO shows how to create random hex keys, but not
how to create random ascii keys. The online Red Hat docs (for
RHEL4, at:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/security-guide/s1-ipsec-generalconf.html
and the next two pages) don't mention how to create secure ascii keys
and refers to the ipsec HOWTO as well.

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

FC3 and RHEL4

How reproducible:

Every time

Steps to Reproduce:
1. Put a hex key in the config file (with or without 0x prefix)
2.
3.
  
Actual results:

Failure due to key length mismatch

Expected results:

Should realise that its a hex key from its length and then
format it correctly for setkey to parse.

Additional info:
Comment 1 Bill Nottingham 2005-03-28 22:18:23 UTC 
Created attachment 112401 [details]
a patch for this

This assumes any key prefixed with '0x' is hex, otherwise, it's ASCII.

Should be backwards-compatible.
Comment 2 Bill Nottingham 2005-03-28 22:19:05 UTC 
Will be in initscripts-8.06-1.
Comment 3 Bill Nottingham 2005-03-31 21:01:09 UTC 
*** Bug 150579 has been marked as a duplicate of this bug. ***
Comment 4 Bill Nottingham 2005-04-05 18:06:14 UTC 
*** Bug 153723 has been marked as a duplicate of this bug. ***