←back to thread

Private Cloud Compute Security Guide

(security.apple.com)
295 points djoldman | 4 comments | 06 Nov 24 13:48 UTC | HN request time: 0.431s | source
1. h1fra ◴[06 Nov 24 16:32 UTC] No.42064796[source]▶
Love this, but as an engineer, I would hate to get a bug report in that prod environment, 100% don't work on my machine and 0% reproducibility
replies(2): >>42065599 #>>42066947 #
2. slashdave ◴[06 Nov 24 17:17 UTC] No.42065599[source]▶
That's a strange point of view. Clearly one shouldn't use private information for testing in any production environment.
replies(1): >>42066832 #
3. ericlewis ◴[06 Nov 24 18:24 UTC] No.42066832[source]▶
As a person who works on this kinda stuff I know what they mean. It’s very hard to debug things totally blind.
4. pjmlp ◴[06 Nov 24 18:30 UTC] No.42066947[source]▶
Usually quite common when doing contract work, where externals have no access to anything besides a sandbox to play around with their contribution to the whole enterprise software jigsaw.