Bug 1403242 – Samba can not access trusted domains through transitive trusts

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1403242 - Samba can not access trusted domains through transitive trusts

Summary:	Samba can not access trusted domains through transitive trusts

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	samba (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Andreas Schneider
QA Contact:	Robin Hack
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-12-09 08:37 EST by Andreas Schneider
Modified:	2017-08-01 14:19 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	samba-4.6.0-0.1.rc3.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-01 14:19:59 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Samba Project	8630	None	None	None	2016-12-09 08:37 EST
Red Hat Product Errata	RHSA-2017:1950	normal	SHIPPED_LIVE	Low: samba security, bug fix, and enhancement update	2017-08-01 14:09:24 EDT

Groups: None (edit)

Description Andreas Schneider 2016-12-09 08:37:00 EST

+------------------+                +------------------+
|                  |                |                  |
| FOREST1 DOM ROOT <----------------+ FOREST2 DOM ROOT |
|                  |   two-way      |                  |
+------------------+    trust       +--------+---------+
                                             ^
                                             |
        ^                                    |
        |                            +-------+-------+
        |                            |               |
        |                            | CHILD.FOREST1 |
        |                            |               |
        |                            +-------+-------+
        |                                    ^
        |                                    |
        |                                    |
        | LOGIN                         +----+----+
        | FOREST1\Administrator         |         |
        +------------------------+      | WINBIND |
                                        |         |
                                        +---------+


WINBIND is a Linux machine and is joined to CHILD.FOREST1. Now a user from FOREST1 wants to login to WINBIND. This does not work and is known to be broken since 2011.

It can be fixed if the user does not want login (ssh) to the machine but access a Samba share.


P.S: This bug will track ONLY for this scenario. If you/the cusomter have different domain setup, open a new bug!

Comment 5 Andreas Schneider 2017-01-09 08:50:13 EST

I configured the domains like described above and used Samba 4.2.10. I'm not able to get it in a working state with Samba 4.2.10.

Comment 7 Andreas Schneider 2017-01-16 05:11:10 EST

This is from Samba 4.6rc1:


samba-cli01:~ # wbinfo --online-status
BUILTIN : online
SAMBA-CLI01 : online
MARS : online
EARTH : online
samba-cli01:~ # getent passwd BERLIN+administrator
BERLIN+administrator:*:500000500:500000513::/home/BERLIN/administrator:/bin/bash

BERLIN is a child domain of EARTH
EARTH and MARS have a two-way trust



We fixed this issue and the fix will be in Samba 4.6 and this in RHEL 7.4!

Comment 12 Andreas Schneider 2017-02-15 09:13:46 EST

I don't know why this worked on samba-4.2.10 I'm not able to create a working scenario with 4.2.10.

Comment 24 errata-xmlrpc 2017-08-01 14:19:59 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1950

Note You need to log in before you can comment on or make changes to this bug.