5 Commits (ca91c244ef1ba7eac6643d66a5fc56d3a2a8b550)

Author	SHA1	Message	Date
Hennadii Stepanov	306ccd4927	scripted-diff: Bump copyright headers ... -BEGIN VERIFY SCRIPT- ./contrib/devtools/copyright_header.py update ./ -END VERIFY SCRIPT- Commits of previous years: - 2021: f47dda2c58 - 2020: fa0074e2d8 - 2019: aaaaad6ac9	2 years ago
MacroFake	fa7a711a30	test: Fix out-of-range port collisions	2 years ago
Hennadii Stepanov	f47dda2c58	scripted-diff: Bump copyright headers ... -BEGIN VERIFY SCRIPT- ./contrib/devtools/copyright_header.py update ./ -END VERIFY SCRIPT- Commits of previous years: * 2020: fa0074e2d8 * 2019: aaaaad6ac9	3 years ago
MarcoFalke	fac23c2114	scripted-diff: Bump copyright headers ... The previous diff touched most files in ./test/, so bump the headers to avoid having to touch them again for a bump later. -BEGIN VERIFY SCRIPT- ./contrib/devtools/copyright_header.py update ./test/ -END VERIFY SCRIPT-	3 years ago
Vasil Dimov	2feec3ce31	net: don't bind on 0.0.0.0 if binds are restricted to Tor ... The semantic of `-bind` is to restrict the binding only to some address. If not specified, then the user does not care and we bind to `0.0.0.0`. If specified then we should honor the restriction and bind only to the specified address. Before this change, if no `-bind` is given then we would bind to `0.0.0.0:8333` and to `127.0.0.1:8334` (incoming Tor) which is ok - the user does not care to restrict the binding. However, if only `-bind=addr:port=onion` is given (without ordinary `-bind=`) then we would bind to `addr:port` _and_ to `0.0.0.0:8333` in addition. Change the above to not do the additional bind: if only `-bind=addr:port=onion` is given (without ordinary `-bind=`) then bind to `addr:port` (only) and consider incoming connections to that as Tor and do not advertise it. I.e. a Tor-only node.	3 years ago