Second, Backplane really looked like great tech https://www.youtube.com/watch?v=43wFJBRTHG0
1,251 karma · joined January 9, 2014
Second, Backplane really looked like great tech https://www.youtube.com/watch?v=43wFJBRTHG0
Any idea why Apple does not provide a service to test whether a device serial number is DEP-managed?
Because once you know the serial number of a DEP device you can enroll into the MDM. There is virtually no security. See https://duo.com/labs/research/mdm-me-maybe
That's all commercial vendors do, push these XML files to your device.
DEP is not required for the VPN profile configs, that can be applied with just MDM (or even manually). The VPN payloads are documented here https://developer.apple.com/enterprise/documentation/Configu...
https://duo.com/labs/research/mdm-me-maybe https://i.blackhat.com/us-18/Thu-August-9/us-18-Endahl-A-Dee...
The code from go kit and [oklog](https://github.com/oklog/oklog) are great examples of idiomatic Go. Unfortunately the community at large doesn't really follow the "no init"/"no package global vars", which can sometimes lead to bad experiences importing opensource Go libs.
I have a few services which were using Go’s acme/autocert package. I now need to update them to the HTTP challenge.
I like mage because it would eliminate a lot of make and bash silliness, but I also want to get into Bazel because of all the things it promises.
Also by a Google engineer and using Google Cloud products, but it’s actually a lot of fun to watch.
It's exciting to see that TUF is now a CNCF project.
It's doable, but it was hard and while cobra is a nice library, it's probably overkill unless you're a project like kubernetes.
Most projects in Go are very small in terms of configuration surface, and something like https://github.com/kolide/launcher/blob/9dcf149957b9e9757a24... is much cleaner IMO.
We have various ongoing efforts to document and improve the macOS experience for users. If you have a macOS question, you'll likely find the answer there.
go-kit and oklog are also fantastic. Peter Bourgon has written a good article about Go best practices and his open source projects really aim for clean, readable code.
Also join the go slack if you haven't yet.
With OS X keychain(and browser) unfortunately, if your system is compromised, you can decrypt the password store.
Software like https://github.com/google/santa can help, especially if you're doing IT in a large enterprise.
The feed used by the software's autoupdate framework(sparkle) was signed, so that would've prevented bad downloads through autoupdate.
Due to the nature of the plug system, you'll have to build caddy yourself if you add customizations like that.
I would agree that the Clock interface is a bit large. In personal projects I prefer to just have something simple like timer func() time.Time
Thanks for blogging about your work on juju! Despite Go already being five years old, many of the patterns around building large applications are only emerging now.
Curious, since it was just you writing the backend, what was the reasoning behind doing microservices + react SPA. Both of those require a lot of commitment, and coordination. Microservices especially are something I'd be more likely to consider with a very large team/many teams instead of a single developer.
Would you choose a microservice architecture again?
Thank you for all the work you do on the ingress project by the way.