6 ms·

Be aware there are a few concerning open issues like it blocking all network requests when disabled: https://github.com/objective-see/LuLu/issues/264 https://gi

Be aware there are a few concerning open issues like it blocking all network requests when disabled: https://github.com/objective-see/LuLu/issues/264 https://github.com/objective-see/LuLu/issues/264 or not being able to login after installing (due to security patch needing to be installed) https://github.com/objective-see/LuLu/issues/284 https://github.com/objective-see/LuLu/issues/284

swiley 6y ago
What a nice and user friendly operating system.
- ecf 6y ago
  What kind of argument is this? It’s a single app... how can you judge an operating system off of something that a) probably hasn’t been updated to support changes or b) kinda buggy because it happens to be a fairly invasive program.
  - a1369209993 6y ago
    Without saying anything about OSX in particular, any operating system that requires network access to log in is a user-hostile piece of shit, and the linked bug#284 pretty well implies that that is in fact the case. It's entirely possible that the problem is due to incompatibities with new OS code or bugs in the firewall program (edit: ie, your case a and case b), but evidence in the bug report pretty clearly suggests that the firewall is correctly blocking all non-whitelisted network requests, and the failure to log in is due to the OS maliciously trying to phone home against the user's wishes.
    - acdha 6y ago
      You're making a mistake jumping to the assumption of malice rather than thinking about all of the other possibilities. This class of bugs is pretty common: people sometimes test software without a network connection at all but its far less common to test with one which drops packets but does not return errors. I've had to fix variations of this problem on Windows, Linux, and things like VMware's HA module. My guess would be that it's something like checking for things like application revocation or other updates or, if you have iCloud enabled, something like attempting to synchronize your settings or data.
      - a1369209993 6y ago
        No, I'm concluding either malice or incompetence-to-the point-of-being-indistinguishable-from-malice, based on the premise that login (to the local computer, when the end user has not explicitly configured it to) involves any network interaction at all. It might not be true that OSX login involves network IO (as I more or less admitted above, I haven't checked), but that was not a assumption I jumped to.
      - swiley 6y ago
        >its far less common to test with one which drops packets but does not return errors. That sounds pretty common to me.
        acdha 6y ago
        That hasn’t been true in my experience using software from Microsoft, Google, Apple, Signal, etc. It seems like most projects only get serious about that after user outcry unless they’re staffed by very experienced engineers.
e40 6y ago
Both issues with Big Sur. An operating system I won't be running for 9-12 months. I'm confident the issues will be cleared up by then.

swiley 6y ago

What a nice and user friendly operating system.

ecf 6y ago
What kind of argument is this? It’s a single app... how can you judge an operating system off of something that a) probably hasn’t been updated to support changes or b) kinda buggy because it happens to be a fairly invasive program.
- a1369209993 6y ago
  Without saying anything about OSX in particular, any operating system that requires network access to log in is a user-hostile piece of shit, and the linked bug#284 pretty well implies that that is in fact the case. It's entirely possible that the problem is due to incompatibities with new OS code or bugs in the firewall program (edit: ie, your case a and case b), but evidence in the bug report pretty clearly suggests that the firewall is correctly blocking all non-whitelisted network requests, and the failure to log in is due to the OS maliciously trying to phone home against the user's wishes.
  - acdha 6y ago
    You're making a mistake jumping to the assumption of malice rather than thinking about all of the other possibilities. This class of bugs is pretty common: people sometimes test software without a network connection at all but its far less common to test with one which drops packets but does not return errors. I've had to fix variations of this problem on Windows, Linux, and things like VMware's HA module. My guess would be that it's something like checking for things like application revocation or other updates or, if you have iCloud enabled, something like attempting to synchronize your settings or data.
    - a1369209993 6y ago
      No, I'm concluding either malice or incompetence-to-the point-of-being-indistinguishable-from-malice, based on the premise that login (to the local computer, when the end user has not explicitly configured it to) involves any network interaction at all. It might not be true that OSX login involves network IO (as I more or less admitted above, I haven't checked), but that was not a assumption I jumped to.
    - swiley 6y ago
      >its far less common to test with one which drops packets but does not return errors. That sounds pretty common to me.
      - acdha 6y ago
        That hasn’t been true in my experience using software from Microsoft, Google, Apple, Signal, etc. It seems like most projects only get serious about that after user outcry unless they’re staffed by very experienced engineers.

e40 6y ago

Both issues with Big Sur. An operating system I won't be running for 9-12 months. I'm confident the issues will be cleared up by then.