-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
App "KDEConnect" cannot be allowed/bypassed #1507
Comments
KDE Connect likely uses P2P/LAN? If so, try enabling:
Some prev refs: |
Thanks, excluding private IPs did do the trick. |
I think that there should be some FOSS apps which should be on the exclude list by default or have at least some rules to have them working by default. What do you think? |
Imposing allowlists/whitelists on unsuspecting users is a landmine. The ones who use apps like KDE Connect or Syncthing already know enough to look for and understand the workarounds, imo. |
I didn't and I guess the others in this issue as well in #577 or #1159 did neither. How about a middle ground where the first blocked request of a well-known FOSS app that's logged will cause a notification saying something like "Hey, it looks like you're using $app and we blocked the request for you which will lead to some functions not working." and then having two options "Allow request for $app" "Dismiss and don't ask again". |
App "KDEConnect" cannot be allowed/bypassed in Rethink.
Symptoms:
Solution/Workaround:
pause or disable Rethink seamlessly works until re-activation of the firewall.
Desired:
Do not stop/pause the firewall to make local connections.
The text was updated successfully, but these errors were encountered: