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: PiStrong
Date: Tue, 25 Sep 2018 10:08:52 +0100	[thread overview]
Message-ID: <c886a75a5928dedb16df2ff53c89bd61bc956755.camel@ipfire.org> (raw)
In-Reply-To: <5835369E-F7F3-4F89-8ACA-41DE98F28DBF@rymes.com>

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

Hey Tom,

thanks for that link.

I had a quick browser around and looked at the code. It is a little bit chaotic
because it is not written in a very Python-y way. Everything is in a function
and the author didn't use any classes. Probably would have been better written
in shell script.

However, there are some more flaws in it regarding the strongSwan configuration
(weakest crypto being tried first) and that is not a good foundation.

What is the solution you are looking for? Making RW work with IPsec for mobile
devices?

Best,
-Michael

On Mon, 2018-09-24 at 20:59 -0400, Tom Rymes wrote:
> Ack. My first thought was that this was for Raspbery Pi, but then no mention
> was made, so I sent this message. Further reading seems to indicate that it is
> for Pi devices. Regardless, perhaps some of the work could be adopted to help
> improve the roadwarrior IPSec experience?
> 
> Tom
> 
> > On Sep 24, 2018, at 8:45 PM, Tom Rymes <trymes(a)rymes.com> wrote:
> > 
> > I saw this on the Strongswan users list, so I’m sure you are all already
> > aware of it, but I don’t know if it has any potential use for IPFire.
> > 
> > Tom
> > 
> > https://github.com/gitbls/pistrong/tree/master
> 
> 


           reply	other threads:[~2018-09-25  9:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5835369E-F7F3-4F89-8ACA-41DE98F28DBF@rymes.com>]

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=c886a75a5928dedb16df2ff53c89bd61bc956755.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