3ce2e95a5f
This all works fine. But it doesn't check repository sizes yet, and without repository size checking, once a repository gets full, there will be no other repository that will want its files. Use of sha2 seems unncessary, probably alder2 or md5 or crc would have been enough. Possibly just summing up the bytes of the key mod the number of repositories would have sufficed. But sha2 is there, and probably hardware accellerated. I doubt very much there is any security benefit to using it though. If someone wants to construct a key that will be balanced onto a given repository, sha2 is certianly not going to stop them. |
||
|---|---|---|
| .. | ||
| adjusted_branches | ||
| assistant | ||
| balanced_preferred_content | ||
| encryption | ||
| exporting_trees_to_special_remotes | ||
| external_backend_protocol | ||
| external_special_remote_protocol | ||
| git-remote-daemon | ||
| iabackup | ||
| metadata | ||
| new_repo_versions | ||
| p2p_protocol | ||
| p2p_protocol_over_http | ||
| requests_routing | ||
| adjusted_branches.mdwn | ||
| assistant.mdwn | ||
| balanced_preferred_content.mdwn | ||
| caching_database.mdwn | ||
| encryption.mdwn | ||
| exporting_trees_to_special_remotes.mdwn | ||
| external_backend_protocol.mdwn | ||
| external_special_remote_protocol.mdwn | ||
| gcrypt.mdwn | ||
| git-remote-daemon.mdwn | ||
| iabackup.mdwn | ||
| importing_trees_from_special_remotes.mdwn | ||
| metadata.mdwn | ||
| new_repo_versions.mdwn | ||
| p2p_protocol.mdwn | ||
| p2p_protocol_over_http.mdwn | ||
| passthrough_proxy.mdwn | ||
| preferred_content.mdwn | ||
| requests_routing.mdwn | ||
| roadmap.mdwn | ||