Commit 012c2151344e984e9a9d4459b44d3e4c818a892f
Minor tweaks to layout, remove TODO (if we want that do it in a seperate md I think)
Anders Rune Jensen committed on 9/12/2018, 11:22:11 AMParent: c5d2f2a9a733cae7847e58749113d298c9f613a0
Files changed
README.md | changed |
README.md | ||
---|---|---|
@@ -49,14 +49,10 @@ | ||
49 | 49 … | |
50 | 50 … | }, |
51 | 51 … | ``` |
52 | 52 … | |
53 | -If you want to use [TOR](https://torproject.org) to create outgoing connections you can specify your `outgoing` like this. It will use `localhost:9050` as the socks server for creating this. | |
53 … | +If you want to use [Tor](https://torproject.org) to create outgoing connections you can specify your `outgoing` like this. It will use `localhost:9050` as the socks server for creating this. | |
54 | 54 … | |
55 | -TODO: | |
56 | -* make the onion socks server configurable. | |
57 | -* support creating hidden services via `incoming` blocks | |
58 | - | |
59 | 55 … | ```json |
60 | 56 … | "connections": { |
61 | 57 … | "outgoing": { |
62 | 58 … | "onion": [{ "transform": "shs" }] |
@@ -68,16 +64,10 @@ | ||
68 | 64 … | |
69 | 65 … | ```json |
70 | 66 … | "incoming": { |
71 | 67 … | "net": [ |
72 | - | |
73 | - { "scope": "public", "external": ["cryptop.home"], | |
74 | - "transform": "shs", "port": 8008 | |
75 | - }, | |
76 | - | |
77 | - { "scope": "private", | |
78 | - "transform": "shs", "port": 8008, "host": "internal1.con.taine.rs" | |
79 | - }, | |
68 … | + { "scope": "public", "external": ["cryptop.home"], "transform": "shs", "port": 8008 }, | |
69 … | + { "scope": "private", "transform": "shs", "port": 8008, "host": "internal1.con.taine.rs" }, | |
80 | 70 … | ] |
81 | 71 … | }, |
82 | 72 … | ``` |
83 | 73 … | |
@@ -86,14 +76,10 @@ | ||
86 | 76 … | That beeing said, the overhead of encryption for local applications can be very high, especially on low-powered devices. For this use-case there is a `noauth` transform which by-passes the authentication and grants full access to anybody that can connect to it. **hint:** *This is risky! it might expose private messages or enables people to publish as you!* Therefore be sure to bind the listener to `localhost` or use the `unix` socket. The `unix` file socket is creted as `$HOME/.ssb/socket` by default and has permissions such that only the user running `sbot server` can open it, just like the `.ssb/secret` file. |
87 | 77 … | |
88 | 78 … | ```json |
89 | 79 … | "incoming": { |
90 | - "unix": [{"scope":"local", "transform":"noauth"}], | |
91 | - "net": [{ | |
92 | - "scope": "local", "transform": "noauth", | |
93 | - "port": 8009, "host": "localhost" | |
94 | - } | |
95 | -] | |
80 … | + "unix": [{ "scope":"local", "transform":"noauth" }], | |
81 … | + "net": [{ "scope": "local", "transform": "noauth", "port": 8009, "host": "localhost" }] | |
96 | 82 … | }, |
97 | 83 … | ``` |
98 | 84 … | |
99 | 85 … | ## License |
Built with git-ssb-web