git-annex/P2P
Joey Hess 1bfe7f8a53
honor preferred content settings of cluster nodes
Except when no nodes want a file, it has to be stored somewhere, so
store it on all. Which is not really desirable, but neither is having to
pick one.

ProtoAssociatedFile deserialization is rather broken, and this could
possibly affect preferred content expressions that match on filenames.

The inability to roundtrip whitespace like tabs and newlines through is
not a problem because preferred content expressions can't be written
that match on whitespace such as a tab. For example:

joey@darkstar:~/tmp/bench/z>git-annex wanted  origin-node2 'exclude=*CTRL-VTab*'
wanted origin-node2
git-annex: Parse error: Parse failure: near "*"

But, the filtering of control characters could perhaps be a problem. I think
that filtering is now obsolete, git-annex has comprehensive filtering of
control characters when displaying filenames, that happens at a higher level.
However, I don't want to risk a security hole so am leaving in that filtering
in ProtoAssociatedFile deserialization for now.
2024-06-25 11:43:09 -04:00
..
Address.hs Windows: Support long filenames in more (possibly all) of the code 2023-03-01 15:55:58 -04:00
Annex.hs disk free checking for unsized keys 2024-01-16 14:29:10 -04:00
Auth.hs update licenses from GPL to AGPL 2019-03-13 15:48:14 -04:00
IO.hs git-annex-shell: block relay requests 2024-06-10 14:16:27 -04:00
Protocol.hs honor preferred content settings of cluster nodes 2024-06-25 11:43:09 -04:00
Proxy.hs honor preferred content settings of cluster nodes 2024-06-25 11:43:09 -04:00