1 | | warner: regarding handling pre-allocated keys, in 0.15.1 it only really handles "`HiddenServiceDir`"-based ones. Then, you pass `hidden_service_dir=` to any of `.system_tor`, `.global_tor` or `.private_tor` class-methods. |
| 1 | warner: regarding handling pre-allocated keys, in 0.15.1 txtorcon only really handles "`HiddenServiceDir`"-based ones. Then, you pass `hidden_service_dir=` to any of `.system_tor`, `.global_tor` or `.private_tor` class-methods. |
| 2 | |
| 3 | In the 1.0 branch, ephemeral services are supported, and `TCPHiddenServiceEndpoint` learns about `ephemeral=` and `private_key=` kwargs. See http://txtorcon.readthedocs.io/en/release-1.x/txtorcon-endpoints.html#txtorcon.TCPHiddenServiceEndpoint |
| 4 | |
| 5 | You can also pass `privateKey=` in the endpoint strings. |
| 6 | |
| 7 | I'm still working out the details/terminology (and e.g. some things are called `*Onion*` because tor is trying to encourage use of "onion services" vs. "hidden services"). |