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

Limit the enctypes when creating the one-way trusts #3681

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Limit the enctypes when creating the one-way trusts #3681

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2640

  • Created at 2015-04-28 12:50:42 by jhrozek
  • Closed as Invalid
  • Assigned to nobody

This came up on sssd-devel when discussing one-way trust design. I'm
pasting the discussion below:

Another thing to remember is a potential need to limit enctypes you'd be
requesting because camellia ciphers are not know to AD and might cause
issues at some point.

SSSD should not be in the business of creating keytabs, it should only
be allowed to retrieve a precreated key, so SSSD shouldn't care about
enctypes, it will get only those that the FreeIPA code stored in the key
in LDAP.

So this means ipasam needs to limit enctypes when asking for the keys.

Comments


Comment from jhrozek at 2015-04-28 12:51:41

One more message in the thread, by Simo:

Yes it should only ask for encrypts that the AD server on the other side
understand, but only for good measure. The key used is alwasy determined
by the KDC (AD in this case) so having additional keys in the keytab is
not a problem. A problem would rather be to miss enctypes, as the KDC
could decide to encode a ticket/TGT in one of the missing enctypes then
and we would not be able to decrypt.


Comment from jhrozek at 2015-04-28 12:54:06

Sorry, I meant to file this ticket in the freeipa trac..

resolution: => invalid
status: new => closed


Comment from jhrozek at 2017-02-24 14:28:43

Metadata Update from @jhrozek:

  • Issue set to the milestone: NEEDS_TRIAGE
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant