TW
Well, as far as i could see / got notified of: - they register an arbitrary dyndns hostname to point to a distribution host of illegal material (e.g. CSAM), malware...
Update: I updated the 2nd post with the current state of affairs. Also cleaned up this ticket a bit, removed posts that are not useful any more.
One can use the email address also as username for the service, so guess that solves it.
Yes, that is because no-change updates sent to the service don't trigger dns zone updates (neither for main host nor for any related hosts). So, the workaround is to update...
guess this is long solved (or solved after transfering the zone to ns*.thinkmo.de).
No, but updating the code to recent django (see PRs) and keeping out scammmers / letting in legitimate users has higher prio right now.
@dragetd attic and ancient versions of borg supported key material directly derived from the passphrase. We removed that long ago because that means you could never change the passphrase. And...
Current master branch (borg2): ``` % export BORG_REPO=/tmp/b2 % borg rcreate -e none % borg create arch docs --stats Repository: /tmp/b2 Archive name: arch Archive fingerprint: c78bab78f32b9fc0b6650cc9e741966d9809c7b0a64bff6f2c178487f725269f Time (start): Thu,...
Could be related to #6709. I have implemented a fix for borg2.
https://docs.python.org/3/library/socket.html The code in `borg.remote` uses FDs (of stdin, stdout, stderr) and `os.select/read/write/set_blocking`. It seems like `select()` and `setblocking()` can also be used with sockets, so would it be just...