I will be releasing a better fix shortly.
My apologies for the late reply, I was busy moving.
I can confirm that the newly released version no longer contains this bug
and have updated all servers to the latest 5.4.28 version. Thanks for the
fix!
Sincerely,
- Wouter van der Schagt
!DSPA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wouter van der Schagt wrote:
> Thank you for the quick reply!
>
>> Is this in 5.5? What are the steps to reproduce? I added the domain as
>> you did above, and my vusaged binary from trunk is running as expected,
>> returning data for the long domai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wouter van der Schagt wrote:
> No, this is in 5.4.28, not running 5.5 at the moment, I can reproduce by
> creating a long domainname and starting vusaged.
Ah. I see this as well. Looking into this.
- --
/*
Matt BrookingsGnuPG Key FAE0672
Thank you for the quick reply!
Is this in 5.5? What are the steps to reproduce? I added the domain as
you did above, and my vusaged binary from trunk is running as expected,
returning data for the long domain name.
No, this is in 5.4.28, not running 5.5 at the moment, I can reproduce by
cre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wouter van der Schagt wrote:
> I found a bug with long domain names which crashes with a segmentation
> fault when the vusaged is started. We have 1 client with a domainname of
> 57 characters and although it is not the domain name listed below, it
> p
