[Openswan dev] Patch for comment (allows disabling xauth and keeping aggressive)

David McCullough david_mccullough at mcafee.com
Thu Oct 27 19:44:59 EDT 2011

Jivin Paul Wouters lays it down ...
> On Thu, 27 Oct 2011, Tuomo Soini wrote:
> >> I have this sitting in my tree from a debug session (interop with
> >> another stack).  For some reason I wanted xauth off but I still
> >> needed agressive mode (I have no idea why the two are tied together
> >> in the code).
> >>
> >> Can't recall why I wanted the modecfg response unfortunately,  I
> >> think is was to make sure modecfg didn't get used.  Not sure.
> >>
> >> Anyway,  if anyone things any of this is useful I'll clean up and
> >> commit.
> >
> > Please do. This is clearly a bug.
> Indeed, please do,
> It was done in the past to not enable Aggressive Mode, unless you
> needed it to interop with Cisco, in which case you also were required
> to have XAUTH.

Any thoughts on the modecfg reply if we aren't going to handle modecfg.
I really wish I could remember why I needed that in there :-(


David McCullough,      david_mccullough at mcafee.com,  Ph:+61 734352815
McAfee - SnapGear      http://www.mcafee.com         http://www.uCdot.org

More information about the Dev mailing list