<story><title>Apple&apos;s apps bypass firewalls like LittleSnitch and LuLu on macOS Big Sur</title><url>https://twitter.com/patrickwardle/status/1318465421796782082</url></story><parent_chain><item><author>dmd</author><text>If you&amp;#x27;re using Cisco Anyconnect, blame that for that particular keyboard issue.</text></item><item><author>thewebcount</author><text>Oh wow! This probably explains why every now and then when I wake my MacBook Pro from sleep it says no keyboard is connected! I thought I had some hardware problem on a basically brand new machine. Glad to hear it&amp;#x27;s only a stupid software problem!</text></item><item><author>eptcyka</author><text>Apple seems to do all kinds of weird networking _stuff_. For instance, during wakeup, your T2 equipped Macbook will wait for a DNS response and then use said DNS response to synchronize time via NTP before letting the user use the keyboard. Probably checking timestamps on signatures for the keyboard firmware, or something stupid like that. This only happens if it happens to have a default route.&lt;p&gt;Similarly, all macOS machines will test a DHCP supplied default route before applying it by trying to reach something on the internet. So if you happen to have some firewall rules that block internet access, no default route will be applied until the internet check times out.&lt;p&gt;I won&amp;#x27;t share the other sentiments about the above, but is it really that hard to document these behaviors?</text></item></parent_chain><comment><author>ClearAndPresent</author><text>Or Wireguard.&lt;p&gt;The absurdity of sitting in front of a frozen keyboard and trackpad for up to a minute before I can unlock the screensaver on a 2k machine has driven me spare. And now has driven away from these astounding lemons.&lt;p&gt;This is the last Apple laptop for me.</text></comment>
<story><title>Apple&apos;s apps bypass firewalls like LittleSnitch and LuLu on macOS Big Sur</title><url>https://twitter.com/patrickwardle/status/1318465421796782082</url></story><parent_chain><item><author>dmd</author><text>If you&amp;#x27;re using Cisco Anyconnect, blame that for that particular keyboard issue.</text></item><item><author>thewebcount</author><text>Oh wow! This probably explains why every now and then when I wake my MacBook Pro from sleep it says no keyboard is connected! I thought I had some hardware problem on a basically brand new machine. Glad to hear it&amp;#x27;s only a stupid software problem!</text></item><item><author>eptcyka</author><text>Apple seems to do all kinds of weird networking _stuff_. For instance, during wakeup, your T2 equipped Macbook will wait for a DNS response and then use said DNS response to synchronize time via NTP before letting the user use the keyboard. Probably checking timestamps on signatures for the keyboard firmware, or something stupid like that. This only happens if it happens to have a default route.&lt;p&gt;Similarly, all macOS machines will test a DHCP supplied default route before applying it by trying to reach something on the internet. So if you happen to have some firewall rules that block internet access, no default route will be applied until the internet check times out.&lt;p&gt;I won&amp;#x27;t share the other sentiments about the above, but is it really that hard to document these behaviors?</text></item></parent_chain><comment><author>dylan604</author><text>Why not blame the idiotic decision to make this network check just to wake up?</text></comment>