Hi Patrick, I think this would be a nice feature to have, indeed. However, given that I have zero experience with tor, I would need some help with the design of such a feature.
I'm thinking something like this might work: - If you pass --onion on the command line, or set onion: true in the configuration file: require a preconfigured .onion URL in the repository configuration. - If you pass --tor-tunnel on the command line, or set tor-tunnel: true in the configuration file: enable the use of the tor+https configuration, don't use a .onion URL even if it is known. - if you pass --tor on the command line, or set tor: true in the configuration file: use a .onion URL if it exists, but fall back to using tor+https if not. What do you think of this suggestion? Does it make sense? Are the proposed option names sensible? In order to make sure that the data is correct and complete, we would need to be able to validate .onion URLs in the CI jobs, which involves downloading repository metadata and making sure it looks sensible. Do you know if it is possible to reach the tor network from a container? If so, would you be willing to help me work that out? If not, can you make another suggestion as to how to do that? Thanks, -- Verstuurd vanaf mijn Android apparaat met K-9 Mail. Excuseer mijn beknoptheid.
