You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@serf.apache.org by "Branko Čibej (JIRA)" <ji...@apache.org> on 2018/05/19 12:40:00 UTC
[jira] [Commented] (SERF-184) Serf has an expiry date
[ https://issues.apache.org/jira/browse/SERF-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481617#comment-16481617 ]
Branko Čibej commented on SERF-184:
-----------------------------------
I don't think we should do anything about this.
# Software archeologists can fudge their system date themselves.
# Source-based distributions can easily regenerate the certificates (the script for that is included in the source tree).
# {{datefudge}} is tragically platform-specific.
> Serf has an expiry date
> -----------------------
>
> Key: SERF-184
> URL: https://issues.apache.org/jira/browse/SERF-184
> Project: serf
> Issue Type: Bug
> Reporter: Marius
> Priority: Minor
>
> Expiring certificates makes it difficult to build older versions of Serf without manual intervention. This is a big problem for source-based distributions and software archaeologists.
> GnuTLS uses [datefudge|https://packages.debian.org/sid/datefudge] to fake the system time so the package is reproducible forever.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)