serf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James McCoy (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SERF-184) Serf has an expiry date
Date Thu, 05 Dec 2019 12:43:00 GMT

    [ https://issues.apache.org/jira/browse/SERF-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988762#comment-16988762
] 

James McCoy commented on SERF-184:
----------------------------------

{quote}2. Source-based distributions can easily regenerate the certificates (the script for
that is included in the source tree).{quote}

Indeed, that's what I [do|https://salsa.debian.org/jamessan/serf/blob/bdec955c811348060333c925ae014183562f939d/debian/rules#L25-31]
in Debian.  However, that required getting {{create_certs.py}} from trunk, since it isn't
part of the 1.3.x source.

> 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
(v8.3.4#803005)

Mime
View raw message