Skip to content
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

I know how to AllowPublicKeys on the laptop version but how do I restrict access similarly to only specific public keys on the Android APK version? #70

Open
bitcoinmeetups opened this issue Oct 26, 2024 · 7 comments

Comments

@bitcoinmeetups
Copy link

I know how to AllowPublicKeys on the laptop version but how do I restrict access similarly to only specific public keys on the Android APK version?

@neilalexander
Copy link
Member

The Android app doesn't support incoming listeners so it wouldn't really do anything.

@bitcoinmeetups
Copy link
Author

But I can connect to my Android device from another remote unit using Yggdrasil it seems. Shouldn't there be a way to allow only specific public keys to connect considering this?

@neilalexander
Copy link
Member

That's not what AllowedPublicKeys does. It controls who can establish an inbound peering connection. It does not control who can reach your device over the Yggdrasil Network.

@bitcoinmeetups
Copy link
Author

I think generally speaking the users believe and for good reasons that when we set AllowedPublicKeys those are the only ones that can establish an SSH connection or VPN connection to the computer for example. Otherwise it's kind of misleading. For example I have seen at least one other user being happy that it's so easy to make access control and a popular LLM also believes that is how to set access control.

@neilalexander
Copy link
Member

neilalexander commented Oct 27, 2024

Honestly I have toyed with the idea of removing the AllowedPublicKeys option altogether, mostly because as you have pointed out, it is not really clear what it does. (Well, more that the distinction between peering connections and actual Yggdrasil traffic is very fuzzy for many users.)

The main point though is that Yggdrasil does not embed a firewall, so if you want to truly control access to your Yggdrasil IPv6 address, then you need an IPv6 firewall to do so.

We might change things up a bit in v0.6 to make it easier to have a closed-loop setup, whereby only devices with a shared password or so can communicate with each other, but we haven't finalised what that might look like yet.

@neilalexander neilalexander transferred this issue from yggdrasil-network/yggdrasil-go Oct 29, 2024
@bitcoinmeetups
Copy link
Author

For starters and at the very least please update the comment section of the config file so it is very clear that AllowedPublicKeys does not do what people think it does.

@neilalexander
Copy link
Member

Did the other day: yggdrasil-network/yggdrasil-go@ff0ef7f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants