There's so many good shows on Apple TV.
1,400 karma · joined August 17, 2020
There's so many good shows on Apple TV.
> Encryption items specifically designed, developed, configured, adapted or modified for military applications (including command, control and intelligence applications) are controlled by the Department of State on the United States Munitions List.
It was part of the whole crypto wars, and the lawsuit brought by Bernstein vs the United States.
See more:
- https://en.wikipedia.org/wiki/Bernstein_v._United_States - https://en.wikipedia.org/wiki/Crypto_Wars - https://en.wikipedia.org/wiki/Export_of_cryptography_from_th...
However that is a very minor implementation, there is no actual x86 in Apple's ARM.
https://www.sciencedirect.com/science/article/pii/S138376212...
TSO could be implemented by other ARM processors easily as well, to provide the same memory ordering guarantees. Besides that the x86 code is translated by Rosetta to ARM instructions.
This does not feel like a stable foundation/platform to build a future on.
https://man.freebsd.org/cgi/man.cgi?query=setproctitle&aprop...
> Additionally, when you use Maps to make a navigation or directions request, details about your route are sent to Apple, including:
> [...]
> A random identifier, which is created when you ask for directions and exists for the duration of your navigation sessionI wish there was an open standard and one I could easily plug in to. Even just a flashing LED on the side of the meter would work for me.
If you already use something like "Sign in with {Google,Facebook,Twitter,Apple}" you are already doing part of it.
I have built several products now with OIDC support for authentication (not authorization) and it has never taken more than a day or two to wire it up.
Adding support for OIDC is not that difficult. I prefer OIDC over SAML anyway, but neither is that difficult.
Lock support for SSO up behind a paywall, not the actual feature.
The SMB's already have SSO, they just don't enable it for the SaaS products they buy because of the price.
I do work for a number of small businesses and they can't afford the "enterprise cost" for things, so there is a shared password vault instead because there is no centralized management of users.
The small businesses all have some form of SSO available, whether they are using Azure Entra ID or Google Workspaces, they have a central location for users, but the cost is prohibitive for most products to get the upgrade to get access to SAML or OIDC for SSO.
SSO doesn't have to be Google, Azure, Okta, PingFederate, you can run a stand-alone instance of Keycloak for instance and have OIDC and SAML available to provide SSO functionality.
> This customer actually returned the car with a 96% charge, the same as they’d picked it up at.
It specifically states that the customer returned the vehicle with the same "fuel" level as when they rented it.If you go against the grain or the way the OS is built and explicitly disable SIP and do things the OS would normally not allow, you are expected to understand the OS enough to know where things have disappeared to when they disappear.
I don't think Apple should protect the very small minority from themselves.
/dev/disk3s3s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk3s6 on /System/Volumes/VM (apfs, local, noexec, journaled, noatime, nobrowse)
/dev/disk3s4 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
/dev/disk3s2 on /System/Volumes/Update (apfs, local, journaled, nobrowse)
/dev/disk1s2 on /System/Volumes/xarts (apfs, local, noexec, journaled, noatime, nobrowse)
/dev/disk1s1 on /System/Volumes/iSCPreboot (apfs, local, journaled, nobrowse)
/dev/disk1s3 on /System/Volumes/Hardware (apfs, local, journaled, nobrowse)
/dev/disk3s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse, protect, root data)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
Stuff that is located on /System/Volumes/Data is on a non-readonly disk and will not be touched by any updates. You can see folders in /System/Volumes/Data that are also in / and there is some magic overlay that maps certain folders to /System/Volumes/Data automatically. So that files in /usr/local/ are actually stored in /System/Volumes/Data/usr/local.However 32 bit registers and everything will continue to exist, and it will act like todays CPU's that went through the multiple bootstrap rounds to get into 64 bit mode.