Bug 737496 - test_common: test_isvalidname failed
Summary: test_common: test_isvalidname failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nss-pam-ldapd
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 743047
TreeView+ depends on / blocked
 
Reported: 2011-09-12 10:15 UTC by Ondrej Moriš
Modified: 2011-12-06 17:36 UTC (History)
2 users (show)

Fixed In Version: nss-pam-ldapd-0.7.5-10.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 17:36:22 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1705 normal SHIPPED_LIVE nss-pam-ldapd bug fix and enhancement update 2011-12-06 01:02:30 UTC

Description Ondrej Moriš 2011-09-12 10:15:08 UTC
Description of problem:

Self-test fails.

Version-Release number of selected component (if applicable):

nss-pam-ldapd-0.7.5-9.el6
nss-pam-ldapd-0.7.5-8.el6

How reproducible:

100%

Steps to Reproduce:

1. make check
  
Actual results:

...
test_common: test_common.c:46: test_isvalidname: Assertion `!isvalidname("foo\\bar\\")' failed.
/bin/sh: line 5: 23916 Aborted                 (core dumped) ${dir}$tst
FAIL: test_common
...
===========================================================
1 of 7 tests failed

Expected results:

All tests pass.

Additional info:

Self-test was working in nss-pam-ldapd-0.7.5-7.el6, this error was introduced with nss-pam-ldapd-0.7.5-8.el6.

Comment 4 errata-xmlrpc 2011-12-06 17:36:22 UTC
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.

http://rhn.redhat.com/errata/RHBA-2011-1705.html


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