[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: production best-practices for cn=monitor

To: Aaron Bennett <abennett@clarku.edu>
Subject: Re: production best-practices for cn=monitor
From: Michael Ströder <michael@stroeder.com>
Date: Mon, 05 Mar 2012 22:29:21 +0100
Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
In-reply-to: <1C4DF99260C2DC4383032F85493C75AA7E3EFF76F8@john.ad.clarku.edu>
References: <1C4DF99260C2DC4383032F85493C75AA7E3EFF76F8@john.ad.clarku.edu>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Firefox/10.0.2 SeaMonkey/2.7.2

Aaron Bennett wrote:

I’m curious what people think about best practices for cn=monitor in
production environments. Do people generally keep it enabled? Is there a
drawback to keeping it enabled? Are there any specific security or performance
concerns?


I have always enabled it equipped with appropriate ACLs.

Ciao, Michael.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

References:
- production best-practices for cn=monitor
  - From: Aaron Bennett <abennett@clarku.edu>

Prev by Date: Re: <what> in ACL defined by set?
Next by Date: Re: <what> in ACL defined by set?
Index(es):
- Chronological
- Thread