OpenLDAP
Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest

Viewing Software Bugs/7497
Full headers

From: hyc@openldap.org
Subject: ldif_read_record line number overflow
Compose comment
Download message
State:
0 replies:
0 followups:

Major security issue: yes  no

Notes:

Notification:


Date: Wed, 23 Jan 2013 01:46:44 +0000
From: hyc@openldap.org
To: openldap-its@OpenLDAP.org
Subject: ldif_read_record line number overflow
Full_Name: Howard Chu
Version: RE24/master
OS: 
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (78.155.233.73)
Submitted by: hyc


While trying to load a 150 million entry LDIF file using slapadd, it would
finish with no errors but only ~107 million entries were loaded. This turns out
to be because at 20 lines per record, the LDIF file contained 3 billion lines,
and the line number counter is a signed int. And in slapadd, we have the
"jumpline" option to skip some number of input lines, when resuming an
interrupted load. The jumpline defaults to 0, if the input line number is less
than the jumpline the record is silently skipped.

After reading the 2147483647th line of the file, it discards all of the rest
until hitting EOF.

Will fix this by changing the parameter to unsigned long. This is unfortunately
going to require a libldap version bump.
Up to top level
Build   Contrib   Development   Documentation   Historical   Incoming   Software Bugs   Software Enhancements   Web  

Logged in as guest


The OpenLDAP Issue Tracking System uses a hacked version of JitterBug

______________
© Copyright 2013, OpenLDAP Foundation, info@OpenLDAP.org