Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8DB55190D1 for ; Fri, 8 Apr 2016 17:22:40 +0000 (UTC) Received: (qmail 73975 invoked by uid 500); 8 Apr 2016 17:22:40 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 73920 invoked by uid 500); 8 Apr 2016 17:22:40 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 73908 invoked by uid 99); 8 Apr 2016 17:22:39 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Apr 2016 17:22:39 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id BF94DDFCDF; Fri, 8 Apr 2016 17:22:39 +0000 (UTC) From: kiwiflyer To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-9342: Site to Site VPN PFS not... Content-Type: text/plain Message-Id: <20160408172239.BF94DDFCDF@git1-us-west.apache.org> Date: Fri, 8 Apr 2016 17:22:39 +0000 (UTC) Github user kiwiflyer commented on the pull request: https://github.com/apache/cloudstack/pull/1478#issuecomment-207524802 PR https://github.com/apache/cloudstack/pull/872 is going to replacing openswan with strongswan. I believe PFS is depreciated in strongwan, so it might make sense to just remove PFS once 872 is committed. It might be worth while looking at addressing this just in 4.7.x and 4.8.x. Thoughts? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---