Bug 89205 - Don't try to do join without authentication unless explicitly requested
Summary: Don't try to do join without authentication unless explicitly requested
Status: RESOLVED FIXED
Alias: None
Product: realmd
Classification: Unclassified
Component: realmd (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Stef Walter
QA Contact: yelley
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-18 14:36 UTC by Stef Walter
Modified: 2015-04-11 11:28 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
service: Refactor to support per domain supported cred types (15.57 KB, patch)
2015-02-20 21:24 UTC, Stef Walter
Details | Splinter Review
Disable automatic AD joins by default (5.66 KB, patch)
2015-02-20 21:24 UTC, Stef Walter
Details | Splinter Review

Description Stef Walter 2015-02-18 14:36:04 UTC
The realm command and various other realmd clients should not do a join without authentication unless specifically requested.

We should not try to do a join with a preset computer account without authentication (such as an OTP or an admin password). The security of kerberos relies on the shared secret.

This currently occurs with the 'realm' command when used against AD.
Comment 1 Stef Walter 2015-02-20 21:24:15 UTC
Created attachment 113699 [details] [review]
service: Refactor to support per domain supported cred types

This is so specific domains can be configured to support things
like automatic authentication.
Comment 2 Stef Walter 2015-02-20 21:24:18 UTC
Created attachment 113700 [details] [review]
Disable automatic AD joins by default

We only offer them as an option to clients if they have been configured
in the realmd.conf file.

This is because automatic AD joins do not have the mutual authentication
we usually expect with kerberos. The computer account secret is
predictable and not secure enough to be on by default.
Comment 3 Stef Walter 2015-04-11 11:28:43 UTC
Merged.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.