Regression in 8.5: float values are treated as invalid when updating LDAP values

[ralfbecker]

Description

The following code:

<?php
ldap_modify($ds, $dn, ['shadowlastchange' => round(time() / (24*3600))]);

Resulted in this output:

LDAP value must be of type string|int|bool, float given (0)

But I expected this output instead:

no output, the operation succeeded before

Problem is caused by php_ldap_try_get_ldap_value_from_zval and used by he following commit: 636b6a1

I can obviously now cast all these kind of timestamp calculations with round(...) to int: (int)round(...), but this is existing code which worked for 10+ years.

So the question is: was that BC breach intended, or does it make sense to handle that cast to int automatically in php_ldap_try_get_ldap_value_from_zval?

Ralf

PHP Version

PHP 8.5.5 (cli) (built: Apr 11 2026 06:53:07) (NTS)
Copyright (c) The PHP Group
Built by Debian
Zend Engine v4.5.5, Copyright (c) Zend Technologies
    with Zend OPcache v8.5.5, Copyright (c), by Zend Technologies

Operating System

No response

[devnexen]

it might be a willingness to make it stricter but I prefer the author herself answering this.

[ralfbecker]

That code probably also fails on 32 bit systems, where PHP itself will convert the result to float:

	/**
	* Add seconds between 1601-01-01 and 1970-01-01 and multiply by 10000000
	*
	* @param int $unixTime
	* @return int windowsTime
	*/
	public static function convertUnixTimeToWindowsTime($unixTime)
	{
		return ($unixTime + 11644477200) * 10000000;
	}