I was trying to create a new OVPN connection for some road warrior with a name like "abc_user" and got the following error message: > name must only contain characters The same problem has been reported in Bug 10595 for IPsec and not been addressed yet: > 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." I need to create different connections for different people of different companies and therefore would like to implement some naming scheme grouping all those people using a short prefix. Especially because I recognized that the list of available connections in the web-UI seems to be sorted alphabetically as well. This is what I would like to have: * abc_user1 * abc_user2 * def_user1 * xyz_user1 Though, I don't care too much about using underscore, dash, or dot or something like that. An underscore simply has the benefit of not being too common in people's names and instead being pretty common for naming schemes. I do understand that the same connection name is used for file names of certificates, in some (CSV-like?) config file "/var/ipfire/ovpn/ovpnconfig" etc., but at least an underscore should be pretty safe to support and provide a lot of grouping/naming benefit. without an underscore, especially with longer names things are far less readable. Thanks for considering!
(In reply to Thorsten Schöning from comment #0) > I do understand that the same connection name is used for file names of > certificates, in some (CSV-like?) config file "/var/ipfire/ovpn/ovpnconfig" > etc., but at least an underscore should be pretty safe to support and > provide a lot of grouping/naming benefit. without an underscore, especially > with longer names things are far less readable. Yes, it would be possible to support a few more characters, but there will be plenty of places in the rest of the distribution that would have to be touched, too. I suppose this is not a 5 minute job, but I would be happy to accept a patch.