public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: AW: IPsec: Include ipsec.user.conf at the bottom
Date: Tue, 19 May 2015 17:34:38 +0200	[thread overview]
Message-ID: <1432049678.16602.48.camel@ipfire.org> (raw)
In-Reply-To: <op.xyv2k82hcahio0@atl-uetersen.atlantisgmbh.local>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

Yeah I thought that this was going in some of these directions where you
want to add really bad configuration directives like rekey=no. We will
discuss that in the other thread on this list though...

I generally oppose having too many "hidden" include files that can be
used to overwrite the basic configuration. They often give us a headache
when we touch things because eventually we will break some of those
manual settings. We keep telling ourselves that this is fine because we
never said that we supported them any way. But that is not really a
valid point.

The better option should be to not need those files.

-Michael

On Tue, 2015-05-19 at 17:28 +0200, Larsen wrote:
> Just stumbled across this in vpnmain.cgi:
>      "/etc/ipsec.user-post.conf"
> 
> When this file exists, it will be included. So apparently, we were using  
> the wrong file (or the documentation is missing that - I don´t know where  
> my co-worker got it from).
> 
> 
> Lars
> 
> 
> 
> On Tue, 19 May 2015 17:07:41 +0200, Heribert Schorn <Schorn(a)t-online.de>  
> wrote:
> 
> > Hi,
> >
> > I agree withe Larsen suggestions to have the include als at the bottom.  
> > With the include stetment on the top the seteetings of ipsec.user.conf  
> > are overwritten and the connection e.g. to IOS or Android will not work  
> > following the proposal in the wiki or the forum.
> >
> > regards
> > Heribert

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-05-19 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2057840161555b51bd851b23.05965494@email.t-online.de>
2015-05-19 15:28 ` Larsen
2015-05-19 15:34   ` Michael Tremer [this message]
2015-05-19 15:44     ` Larsen

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=1432049678.16602.48.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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