From 92f8620affd59e444d76555e33650e5c2080e5b3 Mon Sep 17 00:00:00 2001 From: cjmarkie Date: Fri, 4 Apr 2025 01:14:55 +0000 Subject: [PATCH 1/4] Added a comment --- .../comment_4_4ae2b9582fa0c122d1a1ef7c347ebd84._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/Disable_checksum_with___96__get_--fast__96__/comment_4_4ae2b9582fa0c122d1a1ef7c347ebd84._comment diff --git a/doc/todo/Disable_checksum_with___96__get_--fast__96__/comment_4_4ae2b9582fa0c122d1a1ef7c347ebd84._comment b/doc/todo/Disable_checksum_with___96__get_--fast__96__/comment_4_4ae2b9582fa0c122d1a1ef7c347ebd84._comment new file mode 100644 index 0000000000..54b4607c80 --- /dev/null +++ b/doc/todo/Disable_checksum_with___96__get_--fast__96__/comment_4_4ae2b9582fa0c122d1a1ef7c347ebd84._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="cjmarkie" + avatar="http://cdn.libravatar.org/avatar/cfcc5894b1cec05bf76d200073dd8977" + subject="comment 4" + date="2025-04-04T01:14:55Z" + content=""" +Ah, thanks! Honestly, I'm okay with this being hard and scary-looking to do, as long as I can find it. I don't see `annex.verify` in `man git-annex-config`. Do those docs need refreshing? +"""]] From 1cf19bda0141dde0e147a0fb5da58519ccc4caef Mon Sep 17 00:00:00 2001 From: yannick Date: Mon, 7 Apr 2025 11:13:44 +0000 Subject: [PATCH 2/4] Added a comment: you're cool --- ...3_60af4cdc7429bdf3929072853099998b._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/users/joey/comment_3_60af4cdc7429bdf3929072853099998b._comment diff --git a/doc/users/joey/comment_3_60af4cdc7429bdf3929072853099998b._comment b/doc/users/joey/comment_3_60af4cdc7429bdf3929072853099998b._comment new file mode 100644 index 0000000000..388cf1a14a --- /dev/null +++ b/doc/users/joey/comment_3_60af4cdc7429bdf3929072853099998b._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="yannick" + avatar="http://cdn.libravatar.org/avatar/d60b72e0322e0661f7942823700d3374" + subject="you're cool" + date="2025-04-07T11:13:43Z" + content=""" +Hey Joey, + +Just wanted to leave you a message to say I think you're cool. I'm Gen Z and just recently I am diving into the world of Open Source and its culture. I just have a lot of fascination for people like you who do great, but really magnificent thing and stay so cool about it, not in the spotlights or whatever. Believe it or not, but I found out about `git annex` from ChatGPT when I asked how I can organize multiple hard drives that I have gather over the years with a lot of duplicate files on them. I want to go to film school you see and I want to organize all the footage I have so I can do cool things with it. + +Anyway it is always a breeze to come from something like ChatGPT to a corner of the internet that is so real. In a way it feels quite intimate to leave a message here on your user page of some thing that you created to explain something else you created! It gives me nostalgia to a time I never experienced. + +Looking forward to learn more about you and the things you do and to figure whether git annex is a fit for me. If it is then I will make sure to tell everybody I know about it because it all looks so cool to me already. + + +Warm regards, +Yannick +"""]] From 96b4292fb3120a565af8c3c91ae333df092d23b1 Mon Sep 17 00:00:00 2001 From: msz Date: Mon, 7 Apr 2025 17:06:15 +0000 Subject: [PATCH 3/4] Added a comment --- ..._7ee9ffdf44d5917f5d6aba324e291cde._comment | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site/comment_3_7ee9ffdf44d5917f5d6aba324e291cde._comment diff --git a/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site/comment_3_7ee9ffdf44d5917f5d6aba324e291cde._comment b/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site/comment_3_7ee9ffdf44d5917f5d6aba324e291cde._comment new file mode 100644 index 0000000000..1b1cc9fb5a --- /dev/null +++ b/doc/todo/encrypt_just_the_annex_on_git+annex_hosting_site/comment_3_7ee9ffdf44d5917f5d6aba324e291cde._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="msz" + avatar="http://cdn.libravatar.org/avatar/6e8b88e7c70d86f4cfd27d450958aed4" + subject="comment 3" + date="2025-04-07T17:06:15Z" + content=""" +I've had the opportunity to revisit this old question of mine, and I'd like to ask some further questions. + +I understand the preference for git+annex remotes to not support encryption. However, I'm not sure how to understand layering the special remote (in particular, in front of a proxy). + +Is this possible with the existing git-annex tooling, or hypothetical? As far as I understand, a proxy 1) has to be a git repo thus cannot have encryption enabled, and 2) can push to an encrypted special remote (which must be a different type than git). It cannot pull encrypted annex keys from one special remote and put them unmodified into another (especially not into an annex-supporting git remote), right? + +The (modified) Forgejo instances we use support git-annex, i.e. git remotes which do not ignore the annex and accept content pushes (I call that git+annex). AFAIK the internal layout of such a Forgejo repository is not different from a bare repository ([DataLad blog: forgejo-anexajo - behind the curtain](https://blog.datalad.org/posts/forgejo-aneksajo/#behind-the-curtain)). The goal would be to have the annex objects sent encrypted to a Forgejo instance, *inside* or *alongside* the git repository. It seems that we would need a \"layer\" sitting on top of a normal git remote - but I don't see what that layer could look like. + +The best proxy set-up I came up with was a like this, with the encrypted remote behind the proxy (I'm using bare repository as the push target - not sure if Forgejo could be bent to our will like that): + +``` +local repository ----> (bare repository on a server) --proxy--> (directory special remote on the same server) + \"origin\" \"storage\" / proxied as \"origin-storage\" +``` +It worked, also with encryption, but the setup has limitations. First, encryption happens server-side. Second, only sharedpubkey encryption does not require private keys to be on the server -- in which case pushing to the proxied \"origin-storage\" works, but getting (necessarily) requires enabling \"storage\" locally. +"""]] From f86370693bdb2189232bbc608d6394e729b51b08 Mon Sep 17 00:00:00 2001 From: matrss Date: Tue, 8 Apr 2025 11:26:29 +0000 Subject: [PATCH 4/4] Spoke with mih and he said this could be useful in the project context --- doc/todo/generic_p2p_socket_transport.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/todo/generic_p2p_socket_transport.mdwn b/doc/todo/generic_p2p_socket_transport.mdwn index 6137b73a0b..d86bb9ed97 100644 --- a/doc/todo/generic_p2p_socket_transport.mdwn +++ b/doc/todo/generic_p2p_socket_transport.mdwn @@ -12,3 +12,5 @@ My understanding is that the current tor p2p support is essentially a special ca This should also make it possible to build e.g. a `git annex enable-yggstack` and `yggstack-annex::.pk.ygg` remote in terms of enable-p2p-socket and `p2p-annex::`, even outside of git-annex itself. What do you think? + +[[!tag projects/INM7]]