+++ /dev/null
-[[!comment format=mdwn
- username="joey"
- subject="""comment 5"""
- date="2025-04-11T17:20:08Z"
- content="""
-Implemented this as the mask special remote.
-
-For example, to make a remote that stores annexed
-files encrypted in the origin remote:
-
- git annex initremote encryptedorigin type=mask remote=origin encryption=hybrid pubkey=id@joeyh.name
-"""]]
--- /dev/null
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 6"""
+ date="2025-04-11T17:20:08Z"
+ content="""
+Implemented this as the mask special remote.
+
+For example, to make a remote that stores annexed
+files encrypted in the origin remote:
+
+ git annex initremote encryptedorigin type=mask remote=origin encryption=hybrid pubkey=id@joeyh.name
+"""]]
--- /dev/null
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 7"""
+ date="2025-04-11T17:23:59Z"
+ content="""
+> Could such a special remote use the same \"transport\" as the underlying remote (thinking of p2p http in particular), which would mean the same authentication & the same set of permissions server side?
+
+Yes, the underlying remote is used as-is, whatever it is.
+"""]]