Like many open source projects, Borg is low on developers. The two points you mention are both known and on the agenda for this year. Since you seem to have experience with crypto, why not add a PR? It's all in Python and fairly readable.

When someone says something is the "holy grail of backups" and it is "gpg-encrypted" I assume it does that well, not it does it poorly right now but might improve in the near future.

Thus his post was valuable to me.

"Why not add a PR" is not a reasonable response to something like this. I'm looking to use a backup system, not create one. If something works so poorly that I'd have to start submitting PRs before using it, I'm far more inclined to go elsewhere.

>> Multithreading has been on the agenda for years and will probably never come, much like improved crypto.

> The two points you mention are both known and on the agenda for this year

This is a rather strange response to the above...

Borg isn't really low on developers, it has high churn, i.e. repels developers.

I'm not sure that's a fair summary. It's very clearly stated that there is authentication performed after encryption.

The MAC should prevent the remote server changing the counter or any encrypted bits.

> When the above attack model is extended to include multiple clients independently updating the same repository, then Borg fails to provide confidentiality

Which is why multiple clients are not supported within the same repository.

They absolutely are supported.