Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
  • Issues 657
    • Issues 657
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 335
    • Merge requests 335
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • aportsaports
  • Issues
  • #10120
Closed
Open
Issue created Mar 16, 2019 by Ver friemelt@Verfriemelt

Why is Strongswan built without --enable-aesni support?

Hi,

i have been wondering for some time that Strongswan is built in alpine linux without —enable-aesni. Is there a special reason for this?

With every new release I build strongswan identical to the apk, only that I add —enable-aesni.

It would be great if this would be supported by default.

Background information about AESNI support in strongswan: https://wiki.strongswan.org/versions/56

Many thanks in advance.

(from redmine: issue id 10120, created on 2019-03-16, closed on 2019-05-09)

  • Changesets:
    • Revision 302749e2 by Natanael Copa on 2019-05-06T16:44:28Z:
main/strongswan: enable aesni on x86_64

ref #10120
  • Revision ad588064 by Natanael Copa on 2019-05-06T16:46:02Z:
main/strongswan: enable aesni on x86_64

fixes #10120

(cherry picked from commit 302749e2d5084f8f091e4614d4393b0d98961c7d)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking