Bug 20167 – kpasswdd auf DC Slaves deaktivieren

Bug 20167 - kpasswdd auf DC Slaves deaktivieren


Summary:	kpasswdd auf DC Slaves deaktivieren

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Kerberos
Version:	UCS 2.4
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.2
Assigned To:	Arvid Requate
QA Contact:	Felix Botner

URL:
Keywords:	interim-1

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-09-29 09:57 CEST by Arvid Requate
Modified:	2013-11-19 06:43 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Cleanup
Max CVSS v3 score:

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

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

Description Arvid Requate

2010-09-29 09:57:32 CEST

Derzeit läuft auch auf aus Systemen der Rolle DC Salve der kpasswdd, er wird dort aber nicht genutzt und könnte bei administrativ angepasster UCR Variable kerberos/adminserver ggf. unerwartetes Verhalten auslösen.

In der Datei /etc/default/heimdal-kdc steht statisch KPASSWDD_ENABLED=yes.

Comment 1 Arvid Requate

2013-07-15 14:29:00 CEST

/etc/default/heimdal-kdc is now shipped by univention-heimdal-kdc as a UCR template. kpasswdd is only started on the domaincontroller_master. Case handling in univention-heimdal-kdc.postinst was straightened a bit.

Comment 2 Felix Botner

2013-07-31 14:40:47 CEST

OK - KPASSWDD_ENABLED=yes in /etc/default/heimdal-kdc nur auf dem UCS Master
OK - Changelog

Comment 3 Stefan Gohmann

2013-11-19 06:43:37 CET

UCS 3.2 has been released:
 http://docs.univention.de/release-notes-3.2-en.html
 http://docs.univention.de/release-notes-3.2-de.html

If this error occurs again, please use "Clone This Bug".