mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2020-02-25 16:16:18 -04:00
parent 9659f1c30f
commit 3497e9e510
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/todo/Provide_a_way_to_white_list_local_networks___40__not_just_specific_IPs__41__/comment_4_620fd718bd2c97a6fa4ce775e311a2d6._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2020-02-25T19:46:02Z"
content="""
Back to the proxy question, I suppose if you have multiple internal
networks and the proxy can only access one of them (eg your DMZ),
then allowing access to the proxy is not as bad as "all".
And then DMZ/24 makes explicit that git-annex can access everything in that
network.
Nor am I opposed to that syntax generally (although as I user, I consider
it pretty opaque TBH, not being in the habit of counting bits in my head).
The only haskell implementation I can find is in the `ip` package,
which would be a new dependency for git-annex.
"""]]