From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: Possible bug in OpenVPN, Core 65
Date: Mon, 07 Jan 2013 09:49:19 -0600 [thread overview]
Message-ID: <assp.0719c91312.50EAEE7F.3040808@dailydata.net> (raw)
In-Reply-To: <1357558628.26961.0.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]
Thank you Alexander, for checking and building the patch.
Michael, thank you for fixing it so rapidly.
And, I do apologize. I ran into this issue while testing several months
ago and apparently did not report it.
Rod
On 01/07/2013 05:37 AM, Michael Tremer wrote:
> Thanks guys.
>
> I merged the patch and it will ship with IPFire 2.13.
>
> Best,
> -Michael
>
> On Mon, 2013-01-07 at 08:36 +0100, Alexander Marx wrote:
>> Hi
>> i can fully acknoledge this.
>> Tried to reproduce your error and found the same problems.
>> i will provide a patch for this.
>>
>>
>>
>> Alexander Marx
>>
>>
>> Fachinformatiker Systemintegration
>>
>>
>>
>>
>> Am 07.01.2013 06:44, schrieb R. W. Rodolico:
>>
>>> See http://forum.ipfire.org/index.php/topic,7365.0.html for information.
>>>
>>> Turns out the CCD does not work if the user has embedded spaces in the
>>> CN (field labeled "User's full name or system hostname:" on Road Warrior
>>> creation screen). I don't remember exactly, but I believe OpenSSL or
>>> OpenVPN itself converts spaces to underscores. You can test this by
>>> creating a user, embedding spaces, and then on the server
>>> cat /var/log/ovpnserver.log
>>>
>>> You will note the Common Name has spaces converted to underscores.
>>>
>>> The solution is to write the ccd file with underscores, ie
>>> $filename =~ s/ /_/gi;
>>>
>>> If someone will point me to the script that creates that, I will be
>>> happy to patch and test, then send you the diff.
>>>
>>> Rod
>>>
>>> NOTE: I have spent a little time looking at this and solving it for an
>>> existing installation, but I intend to pull an old router out and
>>> reconfigure it for a controlled test, unless someone else can verify my
>>> findings independently.
>>>
>>> Rod
>>>
>>>
>>> _______________________________________________
>>> Development mailing list
>>> Development(a)lists.ipfire.org
>>> http://lists.ipfire.org/mailman/listinfo/development
>>
>> _______________________________________________
>> Development mailing list
>> Development(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/development
>
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>
--
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rodo.vcf --]
[-- Type: text/x-vcard, Size: 233 bytes --]
begin:vcard
fn:R. W. Rodolico
n:Rodolico;R. W.
org:Daily Data, Inc.
adr:;;POB 140465;Dallas;TX;75214-0465;US
email;internet:rodo@dailydata.net
title:President
tel;work:214.827.2170
url:http://www.dailydata.net
version:2.1
end:vcard
next prev parent reply other threads:[~2013-01-07 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50EA7AFA.2040400@oab.de>
2013-01-07 11:37 ` Michael Tremer
2013-01-07 15:49 ` R. W. Rodolico [this message]
2013-01-07 5:44 R. W. Rodolico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=assp.0719c91312.50EAEE7F.3040808@dailydata.net \
--to=rodo@dailydata.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox