There was this bit in the debian-devel mailing list
To make this happen for trixie, I don't see how to do it. Anyone having >> the old 'signify' package on their system would get OpenBSD's signifyNo: popcon == 58.
instead of the new 'signify-mail' package after an upgrade. Is that
problem really worth caring about?
If you don't have popcon enabled, why not?
I have it enabled and I'm not seeing a real downside to having it
enabled. What am I missing?
If you don't have popcon enabled, why not?
I have it enabled and I'm not seeing a real downside to having it
enabled. What am I missing?
Do you have a link to instructions for encrypting popcon traffic?
I've already got gnupg installed.
On Thu, Oct 10, 2024 at 1:00 AM Jeffrey Walton wrote:
On Wed, Oct 9, 2024 at 7:40 PM Andy Smith wrote:
[...]
You can encrypt it but that requires (a) a conscious decision to do so, and (b) installing gnupg.
Do you have a link to instructions for encrypting popcon traffic?
I've already got gnupg installed.
popcon is encrypted by default as of version 1.60, assuming you have
not changed the default setting. See <https://popcon.debian.org/FAQ>.
I suppose I'm depending on the Debian developers to patch all of the
known software security issues.
Any help on how to check that assumption?
I don't know how you would check that they are not storing your IP
address but only the anonymised id number. Still, I would be prepared to trust that Debian discards the IP address data very early on.
The bit with zless was worth the post. I'd been doing zcat foo.gz | more
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 07:18:05 |
Calls: | 10,388 |
Calls today: | 3 |
Files: | 14,061 |
Messages: | 6,416,822 |
Posted today: | 1 |