On Thu 2017-10-19 13:04:13 +0200, Alessandro Vesely wrote: > No, it's much faster. They say once every few days, but there are > longer periods of quiescence, irregularly distributed along time. For > details see: > https://github.com/publicsuffix/list/commits/master
I'm aware of the frequency, i've been following it for years :) I'm not convinced that those changes need to be published so quickly, though. > That would not be enough. Many servers run on wheezy or jessie. I think you're suggesting that we should ship -updates for those platforms as well, which sounds not unreasonable to me. > Their best option is to set up a cron job to download the file daily. > A more sophisticated user might download the file to a temporary > directory, compare it to the existing one, and in case they differ > replace the old file and then send a SIGHUP to any daemons which > maintain a memory structure of it. > > Finally, consider issuing updates for all debian versions still enjoying > long term support (https://wiki.debian.org/LTS). Is it better or worse > than the former methods? If a cron job is better, one could be > installed in cron.d... > > What do you reckon? I'm not particularly interested in setting up cronjobs for people that (a) introduce new regular network activity and (b) have dubious cryptographic integrity and public transparency properties. Debian packages already solve problem (b) and they avoid (a) by piggypacking on the standard update channels that the operating system already performs. Can you motivate your concern about daily updates a little more clearly? You seem to have a sense of urgency about them that i don't have. Maybe you're seeing some concern that i'm not seeing, though. --dkg
signature.asc
Description: PGP signature
