Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S strongswan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • DebianDebian
  • strongswan
  • Merge requests
  • !9

Re-enable eap-{dynamic,peap} libcharon plugins

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Lucas Kanashiro requested to merge kanashiro/strongswan:re-enable-some-eap-plugins into debian/master May 21, 2020
  • Overview 1
  • Commits 1
  • Pipelines 1
  • Changes 3

eap-dynamic might be quite useful for users because it allows clients to select an alternative EAP method if the one selected by the server initially is not supported.

eap-peap is still widely used by users because it is what most of the clients implement. It is often used in combination with EAP-MSCHAPv2 to authenticate e.g. WiFi clients (the TLS connection in EAP-PEAP protects the potentially weak password authentication in EAP-MSCHAPv2). For instance, using the same protocol for VPN clients allows reusing the existing AAA infrastructure (AD/RADIUS server).

Edited May 21, 2020 by Lucas Kanashiro
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: re-enable-some-eap-plugins