serf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SERF-184) Serf has an expiry date
Date Sat, 19 May 2018 12:40:00 GMT

    [ 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)

Mime
View raw message