New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to openswan after update from iPhone #78

Open
andrewglass3 opened this Issue May 4, 2014 · 5 comments

Comments

Projects
None yet
3 participants
@andrewglass3

andrewglass3 commented May 4, 2014

Hey hope you can help please?

Recently updated openswan on my debian vpn. Since the update I cant connect via iPhone. It responds with

message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level

Any help would be appreciated :)

Thanks

Andy

@letoams

This comment has been minimized.

Show comment
Hide comment
@letoams

letoams May 4, 2014

Contributor

On Sun, 4 May 2014, andrewglass3 wrote:

Hey hope you can help please?

Recently updated openswan on my debian vpn. Since the update I cant connect via iPhone. It responds with

message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level

Any help would be appreciated :)

It is a bug in the latest debian patch. You can downgrade until they
release an updated fix. The downgrade is only vulnerable to a
crash+restart bug, so you should be safe.

Paul

Contributor

letoams commented May 4, 2014

On Sun, 4 May 2014, andrewglass3 wrote:

Hey hope you can help please?

Recently updated openswan on my debian vpn. Since the update I cant connect via iPhone. It responds with

message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level

Any help would be appreciated :)

It is a bug in the latest debian patch. You can downgrade until they
release an updated fix. The downgrade is only vulnerable to a
crash+restart bug, so you should be safe.

Paul

@andrewglass3

This comment has been minimized.

Show comment
Hide comment
@andrewglass3

andrewglass3 May 18, 2014

Thank you for replying much appreciated :)

andrewglass3 commented May 18, 2014

Thank you for replying much appreciated :)

@andrewglass3

This comment has been minimized.

Show comment
Hide comment
@andrewglass3

andrewglass3 Oct 9, 2014

Any news on this issue? Ive still had problems even on recent versions? Is it purely related to debian/ubuntu? Might have to switch to another distro?

andrewglass3 commented Oct 9, 2014

Any news on this issue? Ive still had problems even on recent versions? Is it purely related to debian/ubuntu? Might have to switch to another distro?

@letoams

This comment has been minimized.

Show comment
Hide comment
@letoams

letoams Oct 11, 2014

Contributor

No, it is present in all recent versions of openswan as upstream did not apply the full patch from libreswan. Libreswan does not have this issue. So you can either downgrade openswan or migrate to libreswan. Or wait on upstream to fix this issue by pulling in the 2nd half of the libreswan patch

Contributor

letoams commented Oct 11, 2014

No, it is present in all recent versions of openswan as upstream did not apply the full patch from libreswan. Libreswan does not have this issue. So you can either downgrade openswan or migrate to libreswan. Or wait on upstream to fix this issue by pulling in the 2nd half of the libreswan patch

@amurchick

This comment has been minimized.

Show comment
Hide comment
@amurchick

amurchick Sep 17, 2015

Any news? Or all migrated to libreswan?

amurchick commented Sep 17, 2015

Any news? Or all migrated to libreswan?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment