KrbOfferedEncryptionTypes setting isn't always respected

[smashery]

The KrbOfferedEncryptionTypes setting isn't respected if there's already a "matching" ticket in the kerberos cache.

Steps to reproduce

• Setup: clear the kerberos cache (klist -d)
• Use a kerberos-supported module
• Run the module with kerberos auth (should default to AES256)
• Observe the communications in wireshark - will likely be AES256
• Note that the kerberos cache now has tickets (klist)
• Re-run the module, forcibly setting krbofferedencryptiontypes to RC4-HMAC
• Observe the communications in wireshark - should be RC4-HMAC, but is actually AES256
• Delete kerberos tickets: klist -d
• Re-run the module, forcibly setting krbofferedencryptiontypes to RC4-HMAC
• Observe the communications in wireshark - is now RC4-HMAC

Expected behaviour

• If an encryption type is set that does not match tickets in the kerberos cache, it should re-request a Kerberos ticket OR warn the user about this edge case

Tested on metasploit commit: c9dfb7e

[Neustradamus]

To follow :)

[github-actions]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[Neustradamus]

.

[github-actions]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[github-actions]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[github-actions]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

[Neustradamus]

.