Bug 10595 - Oddities with Certificate Names
Summary: Oddities with Certificate Names
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: all All
: Will affect an average number of users Balancing
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords: GoodFirstBug
Depends on:
Blocks: IPSECBUGS
  Show dependency treegraph
 
Reported: 2014-08-19 16:54 UTC by Tom Rymes
Modified: 2018-10-15 13:48 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Rymes 2014-08-19 16:54:48 UTC
I have noticed a few **very** minor oddities with certificate names when setting up IPSec Certificates:

1.) When you use the WUI to create the Root/Host certs for a machine, the 'C' in certificate is capitalized in "Host Certificate", but not in "Root certificate". This is obviously not a big deal, but it ought to be uniform, all the same.

2.) When uploading a remote system's root certificate, you are not able to specify a name that has any spaces in it, even though the local certificate names *DO* have spaces in them. If you try to specify a name with a space in it, you get the error "Name must only contain characters."
Comment 1 Tom Rymes 2015-10-15 23:37:54 UTC
OK, not much of a start, but I did figure out the solution to #1. The English translation file located at /var/ipfire/langs/en.pl contains the offending strings, and I would suggest changing line 1967 from 

'root certificate' => 'Root certificate',

to

'root certificate' => 'Root Certificate',

Is there somewhere that I should place this, or is here enough? attach a modified file?

I will try to figure out the portion of vpnmain.cgi that controls the form validation for #2, but that's way beyond my skillset.