search

xelerance / Openswan

Openswan
Other
849 stars 214 forks source link

Mort/to merge to 2.6.53dev #452

Closed mohicks closed 3 years ago

mohicks commented 3 years ago

This is a rebase + some fixes. It rebases on top of the latest 2.6.52dev instead of the previous base that mcr did most of this development on.

AnatoliChe commented 3 years ago

Sorry for boring, but in this version have deleted null algos, broken CTR and have not implemented GCM algos? 002 "peer1-peer2" #7: initiating Quick Mode RSASIG+ENCRYPT+PFS+UP+IKEv2ALLOW+SAREFTRACK {using isakmp#6 msgid:2e12a172 proposal=aes_ctr(13)_160-hmac_sha1_96(2)_160 pfsgroup=OAKLEY_GROUP_MODP1024} 003 "peer1-peer2" #7: ESP transform ID of ISAKMP Transform Payload (ESP) has an unknown out value: 0 And this version is still bitten by segfault which can be invoke remotely with 100% of reproducing?

letoams commented 3 years ago

At this point openswan has been abandoned for 10 years. Libreswan is older than openswan was an active fork of freeswan.

Why are you still trying to use this ?

On Nov 28, 2020, at 15:21, AnatoliChe notifications@github.com wrote:

 Sorry for boring, but have you deleted null algos, broke CTR and have not implemented GCM algos? 002 "peer1-peer2" #7: initiating Quick Mode RSASIG+ENCRYPT+PFS+UP+IKEv2ALLOW+SAREFTRACK {using isakmp#6 msgid:2e12a172 proposal=aes_ctr(13)_160-hmac_sha1_96(2)_160 pfsgroup=OAKLEY_GROUP_MODP1024} 003 "peer1-peer2" #7: ESP transform ID of ISAKMP Transform Payload (ESP) has an unknown out value: 0 And this version is still bitten by segfault which can be invoke remotely with 100% of reproducing?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

shussain commented 3 years ago

Sorry for boring, but in this version have deleted null algos, broken CTR and have not implemented GCM algos?

Thank you for reporting the issue Anthony.

And this version is still bitten by segfault which can be invoke remotely with 100% of reproducing?

Thank you for reporting that. Our plan is to investigate and address that this week or next.

shussain commented 3 years ago

Thank you for the PR @mohicks

@AnatoliChe The issues you had reported (deleted null algos, broken CTR, etc) are being investigated and we may followup with you later on with more questions.