Live data from Hacker News

Apple’s macOS Ventura – New Security Changes

sentinelone.com

101–110 of 193 posts

Re: Apple’s macOS Ventura – New Security Changes

#101
post #84

> Gatekeeper’s role is to ensure that when users execute some code, that code meets the local system policy. The policy includes checks such as whether the code is validly signed and whether it has been tampered with in certain ways. Weasel-word alert. I never thought I’d see the day when technologists would applaud the gradual death of general-purpose computing, but here we are. A decade from now Apple probably won’…

It is funny to me to read this because I recently joined the Xcode Cloud team to precisely work on this, thinking that I could help Apple make developer’s life easier in the near future, but according to your comment, there are people out there who will consider my team’s work a regression.

Re: Apple’s macOS Ventura – New Security Changes

#102
post #84

> Gatekeeper’s role is to ensure that when users execute some code, that code meets the local system policy. The policy includes checks such as whether the code is validly signed and whether it has been tampered with in certain ways. Weasel-word alert. I never thought I’d see the day when technologists would applaud the gradual death of general-purpose computing, but here we are. A decade from now Apple probably won’…

I disagree. Before Gatekeeper there was no way to define a policy about what code could run, now with Gatekeeper there is. Currently, Apple define a default policy. Users can edit this themselves if they acknowledge the risks. Admins of Macs can also set their own policies.

The ability to have policies is very different from enforcing overly strong policies. Apple seems quite clear that they see iOS as being a platform with a stronger policy, and macOS as being a platform with at least the ability to run a weaker policy.

Edit: also Xcode Cloud isn't what you imply it is/could be, and Apple's moves with Swift being developed in the open suggest to me a very different direction for development. I can't see this ever being locked down, either in terms of technology or policy.

Re: Apple’s macOS Ventura – New Security Changes

#103
post #84

> Gatekeeper’s role is to ensure that when users execute some code, that code meets the local system policy. The policy includes checks such as whether the code is validly signed and whether it has been tampered with in certain ways. Weasel-word alert. I never thought I’d see the day when technologists would applaud the gradual death of general-purpose computing, but here we are. A decade from now Apple probably won’…

It is funny to me to read this because I recently joined the Xcode Cloud team to precisely work on this, thinking that I could help Apple make developer’s life easier in the near future, but according to your comment, there are people out there who will consider my team’s work a regression.

There is no problem with a remote compilation. If anything, it's good to have options.

The problem if someone decides that it's going to be the only option. And another problem is that they can.

So, your work is not regression, and it definitely has a positive use case. It's just that it can also make certain unethical things possible.

Re: Apple’s macOS Ventura – New Security Changes

#105
post #87
post #75

Earlier quoted context omitted.

In 2018 CPUs were still stagnating, so a 2013 CPU would likely be almost as performant as the latest one.

It's not really about the CPU power, more that by 2018 it was well known that the Trashcan Mac Pro was a dead-end design and a soon to have radical refresh.

Absolutely correct it would have been a shitty purchase but one which ought to be supported none the less.

Companies ought to love people who give them thousands for outdated hardware worth hundreds.

Re: Apple’s macOS Ventura – New Security Changes

#106
post #84

> Gatekeeper’s role is to ensure that when users execute some code, that code meets the local system policy. The policy includes checks such as whether the code is validly signed and whether it has been tampered with in certain ways. Weasel-word alert. I never thought I’d see the day when technologists would applaud the gradual death of general-purpose computing, but here we are. A decade from now Apple probably won’…

[deleted]

Re: Apple’s macOS Ventura – New Security Changes

#107
post #3

Am I the only one increasingly frustrated with macOS's naming scheme? I have no idea what the latest version is. Ubuntu versioning gets this right; you can parse their codenames alphabetically to derive the semantic version. But Apple's heuristic here seems to be "throw a dart at a map of California".

nodejs has joined the conversation

Re: Apple’s macOS Ventura – New Security Changes

#108

> " Passkeys aim to solve the problems with passwords " So are you locked in with Apple if you use this, or can you switch all your existing passwords to another "passkey provider/service" ? > " Wave Goodbye to CAPTCHAS " I assume that's Safari only... so this is bad news for Firefox?

> In collaboration with Google, Microsoft and other industry players, Apple has been working on a new logon technology for web and other remote services called ‘passkeys’. I don't think it will be Apple only. However, I am wondering what will happen to services like bitwarden [1] if it is available on other OSes as well. [1] https://bitwarden.com/

What's your concern regarding Bitwarden?

Re: Apple’s macOS Ventura – New Security Changes

#109
post #84

> Gatekeeper’s role is to ensure that when users execute some code, that code meets the local system policy. The policy includes checks such as whether the code is validly signed and whether it has been tampered with in certain ways. Weasel-word alert. I never thought I’d see the day when technologists would applaud the gradual death of general-purpose computing, but here we are. A decade from now Apple probably won’…

It is funny to me to read this because I recently joined the Xcode Cloud team to precisely work on this, thinking that I could help Apple make developer’s life easier in the near future, but according to your comment, there are people out there who will consider my team’s work a regression.

> It is funny to me to read this because I recently joined the Xcode Cloud team to precisely work on this, thinking that I could help Apple make developer’s life easier in the near future, but according to your comment, there are people out there who will consider my team’s work a regression.

how exactly will it be easier than my current workflow of:

- Boot computer

- Press win-key + d

- type the letters "qtc"

- hit enter

- ctrl-alt-shift-

- ready to code

Re: Apple’s macOS Ventura – New Security Changes

#110
post #97
post #90

Earlier quoted context omitted.

I can see why most on HN (and actually outside of HN too) would say a larger trackpad is great, so I think you might indeed be in the minority opinion on this one. Even mainstream reviewers tended to list it as a positive. But butterfly keyboard had been pretty much universally decried as a terrible mistake almost everywhere, including HN.

>But butterfly keyboard had been pretty much universally decried as a terrible mistake almost everywhere, including HN. That was certainly not the case until the reliability problem got magnified in 2018. When the problem has been there since 2016. Before that Butterfly was somehow the holy grail for touch typist.

I remember reactions being more mixed. I and others always wanted more key travel, but I also knew people who loved it.
Post reply on HN