[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ISAKMP problem



well, as of my January 17th cvs up, it won't work *with* the "passphrase:".
I get that group error that the original poster got.  But i guess January
17th isn't exactly current.

Luke

----- Original Message -----
From: Angelos D. Keromytis <angelos@dsl.cis.upenn.edu>
To: Luke Renn <lrenn@etci.com>
Cc: <retrev@csh.rit.edu>; <tech@openbsd.org>
Sent: Monday, February 07, 2000 4:01 PM
Subject: Re: ISAKMP problem


>
> In message <00ec01bf718a$29fc2840$0a83a8c0@localnet>, "Luke Renn" writes:
> >This only took me two months to figure out :(
> >
> >Change your policy file to something like this (exactly like this):
> >
> >KeyNote-Version: 2
> >Comment: This policy accepts ESP SAs from a remote that uses the right
> >password
> >Authorizer: "POLICY"
> >Licensees: "thisismypassphrase"
> >Conditions: app_domain == "IPsec policy" &&
> >            esp_present == "yes" -> "true";
> >
> >note that the "passphrase:thisismypassphrase" isn't there.  leave the
> >"passphrase:" out.  And make you don't have the lines from from the
example
> >that start with $OpenBSD something or other.  Let me know if you have
more
> >problems.
>
> If you're running -current, you must have the "passphrase:" prefix.
> -Angelos
>
>