Jeffrey Altman writes:
> The following commit has been merged to heimdal-7-1-branch.
>
> ...
>
> commit 8ed97b8583e000288b40a14efb901cbaf4c5d5c7 (origin/heimdal-7-1-branch)
> Author: Quanah Gibson-Mount
> Date: Thu May 23 15:06:33 2019 +
>
> Regenerate certs so that they expire before
The following commit has been merged to heimdal-7-1-branch.
There are still additional commits to that branch that must be approved
and merged before Heimdal 7.7.0 will be released.
commit 8ed97b8583e000288b40a14efb901cbaf4c5d5c7 (origin/heimdal-7-1-branch)
Author: Quanah Gibson-Mount
Date: Th
Brian May writes:
> Brian May writes:
>> This implies it should be possible for ap application to request 64 bit
>> time_t, but not sure how.
> I see proposals to setting _TIME_BITS=64 from 2015, however I don't
> actually see any reference to this being implemented yet.
> https://lwn.net/Arti
On 5/23/2019 4:40 AM, Brian May wrote:
> Brian May writes:
>
>> This implies it should be possible for ap application to request 64 bit
>> time_t, but not sure how.
>
> I see proposals to setting _TIME_BITS=64 from 2015, however I don't
> actually see any reference to this being implemented yet.
Brian May writes:
> This implies it should be possible for ap application to request 64 bit
> time_t, but not sure how.
I see proposals to setting _TIME_BITS=64 from 2015, however I don't
actually see any reference to this being implemented yet.
https://lwn.net/Articles/664800/
--
Brian May
Brian May writes:
> My vague understanding is that this might already be possible by
> defining __USE_TIME_BITS64.
I may not have got this exactly right:
/*
* The event structure itself
* Note that __USE_TIME_BITS64 is defined by libc based on
* application's request to use 64 bit time_t.
*
Jeffrey Altman writes:
> Heimdal's hx509 relies on ctime(), gmtime(), strptime() and tm2time()
> all of which are constrained by glibc's concept of time. Please advise
> when Debian provides 64-bit time versions of these functions on i386.
My vague understanding is that this might already be po
Jeffrey Altman writes:
> Our advice to Debian is to replace the certificate with one that has an
> expiration date before 19 Jan 2038 03:14:07 UTC. Otherwise, Debian will
> fail to detect failures of the certificate validation code caused by
> patches that might be applied to OpenSSL.
I somewha
Heimdal's hx509 relies on ctime(), gmtime(), strptime() and tm2time()
all of which are constrained by glibc's concept of time. Please advise
when Debian provides 64-bit time versions of these functions on i386.
Jeffrey Altman
Heimdal Project Manager
smime.p7s
Description: S/MIME Cryptographic
On 5/22/2019 6:25 PM, Brian May wrote:
> To me it really sounds like Heimdal is dropping support for 32 bit
> architectures then.
>
> However Debian doesn't have the luxury of being able to drop the 32 bit
> version of Heimdal, just for the sake of a faulty test. Particularly
> when existing versi
Jeffrey Altman writes:
> Background on this test failure.
>
> The reason that the Heimdal 7.5.0 tests began to fail after they
> previously succeeded is because the failing test relies upon an X.509
> certificate that expired on March 4 2019.
>
> Then post 7.5.0 support was added to support OpenS
Background on this test failure.
The reason that the Heimdal 7.5.0 tests began to fail after they
previously succeeded is because the failing test relies upon an X.509
certificate that expired on March 4 2019.
Then post 7.5.0 support was added to support OpenSSL 1.1 which included
the ability to
Hi all,
> It looks like this is fixed upstream (at least for 64-bit machines):
> https://github.com/heimdal/heimdal/issues/533
If it helps, I just blindly tried applying:
https://github.com/quanah/heimdal/commit/e3cd069e5c40b455541508b81ffeb0563e882aed
… on top of src:heimdal 7.5.0+dfsg-2.1
It looks like this is fixed upstream (at least for 64-bit machines):
https://github.com/heimdal/heimdal/issues/533
On Sun, 10 Mar 2019 06:17:32 -0500 "A. Wilcox"
wrote:
> Source: heimdal
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in
> Source: heimdal
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> heimdal fails to build from source, both in Buster and Sid. It is
> failing in one of the tests. Relevant snippet below and full build log
> is accessible at:
>
Source: heimdal
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
heimdal fails to build from source, both in Buster and Sid. It is
failing in one of the tests. Relevant snippet below and full build log
is accessible at:
https://tests.repr
16 matches
Mail list logo
