And in the docs[0], the manual instructions ask you to run their agent container with --privileged=true, which gives the container access to all devices on the host and more.[1]
Hm.. try to start it without --privileged. WI think it's not necessary now. I don't remember the main reason why we use that flag. Please try without and can you send me feedback about. If it will work good - we'll update installer. Thx you!
You are right. But you can play with our platform this weekends, and on next week we'll opening agent to open-source and enable security. We have some delay with SSL delivery. :(
When I see security as a second-class citizen on user-visible elements, I assume that the same philosophy was applied on the parts I can't audit, even after the front-end stuff was fixed.
I agree. Basically makes me distrust the whole thing inside and out; who knows what other bs engineering practices were used in non visible parts of the stack? Shipping is great, but please don't ship insecure stuff as a product you want customers to use. Please.
You can get HTTPS for free (and hassle-free) if you use Cloudflare as your DNS server. Disclaimer: I am doing this publicity as a happy customer, without earning anything in return.
It's a bit more than DNS. It's sending all of your traffic through cloudflare, and they cache content/act as a CDN. But they can theoretically inspect/modify all traffic.
Looks super neat but I'll pass.
[0] http://lastbackend.com/guide/ [1] https://docs.docker.com/reference/run/