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

[BUG] SSL uses weak encryption (SWEET32) #1275

Open
krunal-git opened this issue Nov 21, 2024 · 2 comments
Open

[BUG] SSL uses weak encryption (SWEET32) #1275

krunal-git opened this issue Nov 21, 2024 · 2 comments
Labels
bug Something isn't working stale No activity within the last 60 days

Comments

@krunal-git
Copy link

Could you please help to address this?
I tried to disable the weak chiphers on the but some pods keep crashing or restarting continuously .

SSL uses weak encryption (SWEET32)

Ports
2379 / tcp
2380 / tcp
6443 / tcp / www
10250 / tcp / www
10349 / tcp / www
10350 / tcp / www

  Medium Strength Ciphers (> 64-bit and < 112-bit key, or 3DES)

    Name                          Code             KEX           Auth     Encryption             MAC
    ----------------------        ----------       ---           ----     ---------------------  ---
    ECDHE-RSA-DES-CBC3-SHA        0xC0, 0x12       ECDH          RSA      3DES-CBC(168)          SHA1
    DES-CBC3-SHA                  0x00, 0x0A       RSA           RSA      3DES-CBC(168)          SHA1

The fields above are :

  {Tenable ciphername}
  {Cipher ID code}
  Kex={key exchange}
  Auth={authentication}
  Encrypt={symmetric encryption method}
  MAC={message authentication code}
  {export flag}

Version (please complete the following information):

  • VEBA Version: [e.g. v0.7.4]

Additional context

@krunal-git krunal-git added the bug Something isn't working label Nov 21, 2024
Copy link

Howdy 🖐   krunal-git ! Thank you for your interest in this project. We value your feedback and will respond soon.

Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the stale No activity within the last 60 days label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale No activity within the last 60 days
Projects
None yet
Development

No branches or pull requests

1 participant