Jamil
Jamil
> Yeah, would definitely be nice to be able to turn on/off without having to redeploy. > > As far as the looks, no objections here. Just out of curiosity,...
> Yeah, that would be really cool to be able to have a banner that is triggered on individual account settings/state. Hm that gets complicated. Do we count offline Gateways...
Closing due to inactivity / unclear requirements.
Maybe we won't need the option to ignore updates if we use a less intrusive update notification, like this notification dot for the daily check? Just thinking about how not...
That post is 10 years and horribly outdated - Gatekeeper has since been introduced with much stricter requirements. The short of it is that this happens for _any_ listen socket...
It looks like it will show up whenever we bind to a publicly listenable address like `0.0.0.0`.
If we had codesigning issues, you can bet that we would have seen them by now... those are incredibly strict, and I wrestled with them for dozens of hours before...
It hasn't only showed up recently though. This has been a thing for some time. I'm not sure why it's inconsistent, however. It likely only happens after installing the client...
I just ran a little experiment on this. I clicked "Deny" and everything still works. No errors logged from connlib or anything else. Which begs the question - what's triggering...
We do this in the Apple and Android clients already. We log to both facilities from within connlib.