I wonder if the scammer is using emails and passwords from a breach against Facebook to access "reputable" accounts and then posting marketplace listings.
I believe what they changed is the ability for "everyone" to discover you to a 10 minute toggle. It defaults to always being discoverable to your contacts.
I assume that it still broadcasts your hashes even in the contacts-only mode, so you'd need to turn receiving off to stop that. Or go a step further and disable Bluetooth entirely* when you don't need it.
* If you disable Bluetooth in the Control Center pulldown it won't actually disable Bluetooth or beacons. It just won't connect to devices. You need to go into Settings to actually disable Bluetooth.
The best I could tell is that it just makes a Docker image for you to deploy to EKS. I’m struggling to see why it’s got OS tacked on the end… it would still seem you’re running Linux and possibly they’ve changed some of the userland?
At first I thought this was going to be a unikernel model like MirageOS[1] is for OCaml, and now I’m disappointed[2].
I'm not sure if I'm reading this correctly. The statements below are my understanding, but it'd be great if you can confirm to provide more color.
The pre-patch setup would just make the implicit trust policy explicit, meaning any user or role in the account with `sts:AssumeRole` on `*` could assume the role (which is still the default when not trust policy is specified).
This change improves the posture by adding a trust policy to the role that prevents any roles other than those two listed from assuming the role. So this is purely a defense in depth measure, and not really a security vulnerability (unless we say the default, implicit trust policy is a security vulnerability itself :P).
Can you share a bit more about how open these roles are to remote candidates?
You list office locations and don't say remote, but then imply remote in the first paragraph. Anecdotally I've heard of people being remote on Apple security teams in the Seattle area, but every time I look at roles on jobs.apple.com they all appears as in office only.
You could be sued for doing something that was potentially considered unsafe by some studies. Business wise it's better to just "play it safe" here with low sodium meals.
> which effectively prevents you from installing linux
This was going to be the state when Microsoft first proposed secure boot. But the backlash lead to (1) being able to disable it and (2) being able to load customer keys.
Are any motherboards actually locked down to where you can't install another OS? My older Gigabyte motherboard, my Thinkpad laptop, and my HP business line desktop all support both of these.
UEFI was definitely a pain point for booting Linux when it was first available. The same Gigabyte motherboard mentioned ended up having it all turned off and just used legacy boot for years. But everything works great with UEFI USB boot installers and the OS. I'd recommend giving it a try again.
I personally use secure boot for Linux through custom keys and a kernel install hook that resigns the EFI+kernel+initramfs+cmdline blob. It's quite nice in combination with LUKS unlocked by TPM2 (similar to Bitlocker). Secure boot actually lets you be more selective in which PCRs to verify for LUKS unlocking, meaning it's much less fragile during updates.
That's not how DownDetector works. It just relies on reports from users. The real failure case is users not understanding why they can't access whatever end service. Maybe they blame that service, maybe they blame their ISP, maybe they blame something else.
It's still there now, on the top of the page, just marked resolved:
us-west-1:
7:52 AM PST We are investigating Internet connectivity issues to the US-WEST-1 Region.
8:01 AM PST We have identified the root cause of the Internet connectivity to the US-WEST-1 Region and have taken steps to restore connectivity. We have seen some improvement to Internet connectivity in the last few minutes but continue to work towards full recovery.
8:10 AM PST We have resolved the issue affecting Internet connectivity to the US-WEST-1 Region. Connectivity within the region was not affected by this event. The issue has been resolved and the service is operating normally.
us-west-2:
7:43 AM PST We are investigating Internet connectivity issues to the US-WEST-2 Region.
8:01 AM PST We have identified the root cause of the Internet connectivity to the US-WEST-2 Region and have taken steps to restore connectivity. We have seen some improvement to Internet connectivity in the last few minutes but continue to work towards full recovery.
8:14 AM PST We have resolved the issue affecting Internet connectivity to the US-WEST-2 Region. Connectivity within the region was not affected by this event. The issue has been resolved and the service is operating normally.