Chef-sugar stands its grounds against ICE contract
1–9 of 9 posts
Re: Chef-sugar stands its grounds against ICE contract
#2Re: Chef-sugar stands its grounds against ICE contract
#3Re: Chef-sugar stands its grounds against ICE contract
#4That's some horrendous infosec. Why would ICE or anyone use this? Can't Chef use, err, Chef or something like that to remove all credentials as soon as employees leave the organization?
Re: Chef-sugar stands its grounds against ICE contract
#5Quite rare to find projects standing its own ground .
Re: Chef-sugar stands its grounds against ICE contract
#6Chef's official stance remains unchanged. Their blogpost: https://blog.chef.io/2019/09/19/chefs-position-on-customer-e...
That should have been Chef's only response, really. (That, and they still need to explain how a former developer somehow managed to break something.)
Re: Chef-sugar stands its grounds against ICE contract
#7Chef's official stance remains unchanged. Their blogpost: https://blog.chef.io/2019/09/19/chefs-position-on-customer-e...
> For context, we began working with DHS-ICE during the previous administration That should have been Chef's only response, really. (That, and they still need to explain how a former developer somehow managed to break something.)
Re: Chef-sugar stands its grounds against ICE contract
#8> Earlier today, a former Chef employee removed several Ruby Gems, impacting production systems for a number of our customers. That's some horrendous infosec. Why would ICE or anyone use this? Can't Chef use, err, Chef or something like that to remove all credentials as soon as employees leave the organization?
Re: Chef-sugar stands its grounds against ICE contract
#9https://blog.chef.io/2019/09/23/an-important-update-from-che...