Skip to content
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

Can't select 3DES encryption algorithm in IKE Proposals. Selection changed to DES. #15316

Closed
cloudcapps opened this issue Feb 29, 2024 · 1 comment
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@cloudcapps
Copy link

Deployment Type

Self-hosted

NetBox Version

v3.7.3

Python Version

3.10

Steps to Reproduce

  1. Cilck into the IKE Proposals section under VPN > Security.
  2. Click to add a new IKE Proposal or edit an existing proposal.
  3. Select 3DES from the encryption algorithm dropdown.
  4. Selection will instantly be changed to DES instead.

Expected Behavior

I should be able to select 3DES as an encryption algorithm.

Observed Behavior

My selection was changed to DES instead.

@cloudcapps cloudcapps added the type: bug A confirmed report of unexpected behavior in the application label Feb 29, 2024
@jeremystretch jeremystretch self-assigned this Feb 29, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Feb 29, 2024
@jeremystretch
Copy link
Member

jeremystretch commented Feb 29, 2024

This is a bug in the form field choices; the value for 3DES is show twice:

        (ENCRYPTION_3DES, '3DES'),
        (ENCRYPTION_3DES, 'DES'),

IPSec proposals are affected as well, as they use the same set of choices. Thanks for catching this!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants