>removing the package would remove /var/cache/apt-cacher-ultra but it doesn't.
I think generally removing a package doesn't remove non-package files. I'm open to the idea that this is wrong though. >But I'm still baffled as to when the cert needs regenerating? The cert it creates is a *CA* cert, which the MITM then uses to create and sign certs for things like deb.debian.org, mega.nz, etc. If you look in the admin interface under "TLS MITM", it'll say something like "CERT CACHE: 11 of 256", those are the server certs that have been generated off the CA. So, adding server names that you want to cache do not require generating and distributing a new CA cert. >But why json by default? It was a call I made, but I don't have a strong opinion on the default there, I'll push out a new release with a few small changes after I have a chance to test it in a bit, and that'll include the switch to text as the default log format and the removal of the time (there is still a case for time in the JSON format since the timestamp exists outside of the JSON entry, but I've removed it from both for the time being, and I can add it back in later if it seems useful. Thanks for the feedback! In my testing, it's still very on track for a mid June 1.0 release. I've run thousands of system installs and thousands of apt update/upgrade cycles and the issues I've run into have been addressed, 0.9.7 has been working great with no adoption failures (the biggest issue I'd been running into; the adoption is the trickiest part but also the most worthwhile WRT surviving DDoS). Sean
