-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardening of remote maintenance via SSH #153
Conversation
5052e13
to
88632ed
Compare
The test for the pinned interface name is flaky, need to check. |
a5414b9
to
a8d3d4e
Compare
I think I managed to fix the tests in a good way, waiting for the network device to show up, but succeeding as soon as it does. Like this we can use a general enough wait without making the test unnecessarily slow. You can see in test output that it just takes a while for ZeroTier to fully start up after the service is started:
On the Action runners this takes much longer than when I run the test locally on my machine. With |
We expect just one network to be required, previous list was likely just for convenience of passthrough to ZT service definition.
We need for system, service and network interface to fully start up.
This allows for setup to take several seconds at times, but lets tests finish as soon as possible when setup is quick.
a8d3d4e
to
f3ea86f
Compare
Looking good, just wondering if you’ve tested the functionality in a real scenario? |
Tests on an actual installation:
|
This limits SSH connections for remote maintenance to come via the known ZeroTier network's interface, and disables unnecessary forwarding options.
Checklist