[horde] Fresh install of horde6.0.0-RC5

[Nels Lindquist]

Hi, Mike.

On 2026-05-28 2:47 PM, Mike wrote:
> 
> I'm doing a fresh install of horde6 and ran into this error:
> 
> Invalid PKCS#7 padding byte: 0xFA
> in /var/www/beta2-horde6/vendor/horde/crypt_blowfish/src/Blowfish.php:202

<SNIP>

> I believe the bcrypt library is installed.
> 
> I'm using:
> 
> Ubuntu Resolute
> php 8.4
> Apache2
> horde6.0.0-RC5
> 
> I installed my version by using this method:
> 
> git clone https://github.com/horde/bundle horde6-beta
> chown -R www-data:www-data horde6-beta
> cd horde6-beta
> composer config minimum-stability beta
> composer install
> composer require horde/imp horde/turba horde/kronolith horde/ingo horde/ 
> nag horde/timeobjects
> 
> cp -a var/config/horde/conf.php.dist var/config/horde/conf.php
> ln -sf ../../../../var/config/horde/conf.php vendor/horde/horde/config/ 
> conf.php
> 
> I tested the install by going to: https://192.168.6.11/horde/test.php 
> and there doesn't seem to be any issues related to Blowfish
> 
> I'm using sqlite as a temporary setup.
> 
> I issued this command:
> 
> vendor/bin/horde-db-migrate
> 
> I'm not sure what I'm missing to make this work.  I probably don't have 
> something configured correctly.

What happens if you set the minimum stability back to "dev" rather than 
"beta" and then do a "composer update -W"?

While the overall project is in the RC stage, I'm noticing with my 
installation that there's at least one library still listed as "alpha5" 
being the most recent version. I presume that if they're stable enough 
as is they'll be designated as RC without changing, but in the meantime 
maybe you've excluded a required dependency inadvertently?


-- 
Nels Lindquist
nlindq at maei.ca