Package: sudo-ldap Version: 1.8.5p2-1+nmu1 Severity: important Tags: patch
Dear Maintainer,
* What led up to the situation?
i wanted to use the sudo.schema in my ldap server but i didn't work,
inserting the schema was refused by openldap
* What exactly did you do (or not do) that was effective (or
ineffective)?
i patched the schema to remove the old attribute name and make openldap
happy.
* What was the outcome of this action?
schema is loading fine
patch is attached to bug report
Cheers
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/
--- sudo.schema 2014-12-17 10:29:49.346595749 -0500
+++ sudo-right.schema 2014-12-17 13:40:35.191999713 -0500
@@ -56,7 +56,7 @@
ORDERING generalizedTimeOrderingMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )
-attributeTypes ( 1.3.6.1.4.1.15953.9.1.10
+attributetype ( 1.3.6.1.4.1.15953.9.1.10
NAME 'sudoOrder'
DESC 'an integer to order the sudoRole entries'
EQUALITY integerMatch
@@ -66,5 +66,4 @@
objectclass ( 1.3.6.1.4.1.15953.9.2.1 NAME 'sudoRole' SUP top STRUCTURAL
DESC 'Sudoer Entries'
MUST ( cn )
- MAY ( sudoUser $ sudoHost $ sudoCommand $ sudoRunAs $ sudoRunAsUser $ sudoRunAsGroup $ sudoOption $ sudoOrder $ sudoNotBefore $ sudoNotAfter $ description )
-)
+ MAY ( sudoUser $ sudoHost $ sudoCommand $ sudoRunAs $ sudoRunAsUser $ sudoRunAsGroup $ sudoOption $ sudoOrder $ sudoNotBefore $ sudoNotAfter $ description ))
signature.asc
Description: This is a digitally signed message part.
