Name: | slapi-nis |
---|---|
Version: | 0.54 |
Release: | 5.el7 |
Architecture: | x86_64 |
Group: | System Environment/Daemons |
Size: | 417951 |
License: | GPLv2 |
RPM: | slapi-nis-0.54-5.el7.x86_64.rpm |
Source RPM: | slapi-nis-0.54-5.el7.src.rpm |
Build Date: | Wed Sep 16 2015 |
Build Host: | x86-ol7-builder-04.us.oracle.com |
Vendor: | Oracle America |
URL: | http://slapi-nis.fedorahosted.org/ |
Summary: | NIS Server and Schema Compatibility plugins for Directory Server |
Description: | This package provides two plugins for Red Hat and 389 Directory Server. The NIS Server plugin allows the directory server to act as a NIS server for clients, dynamically generating and updating NIS maps according to its configuration and the contents of the DIT, and serving the results to clients using the NIS protocol as if it were an ordinary NIS server. The Schema Compatibility plugin allows the directory server to provide an alternate view of entries stored in part of the DIT, optionally adding, dropping, or renaming attribute values, and optionally retrieving values for attributes from multiple entries in the tree. |
- Don't lookup groups in SSSD for memberUid without @domain - Resolves: #1243823
- Fix CVE-2015-0283 for RHEL 7.2 - Resolves: #1202996
- Fix CVE-2015-0283 - Resolves: #1202995
- Complete ID views support to BIND operation - Ignore ID views outside schema-compat subtrees - Use 389-ds API compatible with RHEL 7.0 - Resolves: #1151436
- Add support for IDM's ID views - Allow searching SSSD-provided users as memberUid case-insensitevly - Resolves: #1151436
- backport correction to the default settings for hosts.byname and hosts.byaddr NIS maps, so that their data items start with the host's address rather than a name (#1090948)
- Mass rebuild 2014-01-24
- remove ExclusiveArch if %{rhel} is 7 or higher, because 389-ds-base gets built for everything now (#1055711)
- Mass rebuild 2013-12-27
- correctly reflect whether or not we're built with transaction support in the module's nsslapd-pluginVersion attribute - fix a couple of should've-used-memmove()-instead-of-memcpy() cases which would hit when removing maps or groups of maps (#1043546/#1043638)